<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel">
    <title>gmane.comp.python.enthought.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16931"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16930"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16929"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16928"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16927"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16926"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16925"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16924"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16923"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16922"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16921"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16920"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16919"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16918"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16917"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16916"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16915"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16914"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16913"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16912"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16931">
    <title>Re: [mayavi] Help for standalone decorator script</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16931</link>
    <description>
Jed, do you want to have a go at implementing this? What needs to be done
is to factor out the option parsing from the function called by
standalone, aka the Mayavi app class, in plugins/app.py. Maybe just
subclassing this class with an empty "parse_command_line" method?

Prabhu and I are fighting with our work load, and having a go at this is
a good way to have it done sooner than later.

Cheers,

Gaël
</description>
    <dc:creator>Gael Varoquaux</dc:creator>
    <dc:date>2008-08-30T01:06:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16930">
    <title>Getting started with enthought technology</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16930</link>
    <description>Nice job with the getting started tutorial. In my opinion this really
should be sitting in the wiki. Our wiki is hard to read and hard to
browse. Moreover it is not easy to print, or to download.

How about making this a sphinx document?

My 2 cents,

Gaël
</description>
    <dc:creator>Gael Varoquaux</dc:creator>
    <dc:date>2008-08-30T00:51:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16929">
    <title>Re: Installation difficulties (an understatement)</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16929</link>
    <description>
Can you give a bit more detail why my repository didn't work? Also, can
you tell me when you tried to install through my repo. I fixed a nasty
bug in the Chaco package two days ago.

Cheers,

Gaël
</description>
    <dc:creator>Gael Varoquaux</dc:creator>
    <dc:date>2008-08-29T23:52:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16928">
    <title>Re: Installation difficulties (an understatement)</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16928</link>
    <description>
I haven't attempted to install straight from PyPI , so can't comment
on that method (which should theoretically be the easiest). I can
successfully build and install TraitsGUI+Chaco from trunk onto WinXP
and RHEL5 with python 2.5.1, setuptools, and wxPython 2.8.7.1. There
two difficulties that have caught me in the past. The first is a not
recent enough version of numpy (they have fixed some numpy.distutils
bugs recently) and the second is a not recent enough version of SWIG
(ETS won't build with SWIG 1.3.29 that came with RHEL5 and was in my
cygwin install for a while). My first recommendation is to update
numpy to the latest (1.1.1) and SWIG to something recent (I've tested
both 1.3.31 and 1.3.36). Once I've done that, the following works well
for me:

mkdir ETS
svn co https://svn.enthought.com/svn/enthought/Traits/trunk ETS/Traits
svn co https://svn.enthought.com/svn/enthought/EnthoughtBase/trunk
ETS/EnthoughtBase
svn co https://svn.enthought.com/svn/enthought/TraitsGUI/trunk ETS/TraitsGUI
svn co https:/</description>
    <dc:creator>Alexander Michael</dc:creator>
    <dc:date>2008-08-29T21:26:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16927">
    <title>Re: ETS "trunk" alias now implemented in SVN</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16927</link>
    <description>
It just occurred to me that people should be reminded that the trunk 
directories for all projects are not necessarily the candidates for 
nearest release (we just went through a short-period of having release 
branches for example,) nor are the trunks always guaranteed to work with 
each other (that's one of the reasons we split the repo up into 
projects/dev_line as opposed to the previous dev_line/project).   All 
that being said, most of the time it will be exactly the right thing.

</description>
    <dc:creator>Dave Peterson</dc:creator>
    <dc:date>2008-08-29T19:34:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16926">
    <title>Re: ETS "trunk" alias now implemented in SVN</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16926</link>
    <description>

I just talked with Dave P. about this and he said he can make that  
check (or disbling it) an optional feature.

Alternatively, revert your ETSProjectTools to 21317. :)
</description>
    <dc:creator>Peter Wang</dc:creator>
    <dc:date>2008-08-29T19:09:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16925">
    <title>Re: ETS "trunk" alias now implemented in SVN</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16925</link>
    <description>I get a runtime error when I try "ets develop":

 File "/home/ccasey/ETSProjectTools/enthought/ets/tools/checkouts.py",
line 190, in _validate_parent_dirs
    raise RuntimeError(msg)
RuntimeError: The directory "/home/ccasey/ETS" is an svn checkout, not
an ets checkout!

On the plus side, Eclipse recognizes the fact that my whole ETS project
is under version control.


On Fri, 2008-08-29 at 13:47 -0500, Peter Wang wrote:
</description>
    <dc:creator>Chris Casey</dc:creator>
    <dc:date>2008-08-29T19:07:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16924">
    <title>Re: ETS "trunk" alias now implemented in SVN</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16924</link>
    <description>

I forgot to add that you can still do "ets develop" to build and  
install in-place versions of everything.


-Peter
</description>
    <dc:creator>Peter Wang</dc:creator>
    <dc:date>2008-08-29T18:47:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16923">
    <title>ETS "trunk" alias now implemented in SVN</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16923</link>
    <description>Hey everyone,

After some discussion, I created a top-level "aliases" directory in  
SVN, and added an alias for "trunk" inside that.  I then used SVN  
externals to create links to the trunk of all of the current projects  
that comprise ETS (based on looking at the setup.py for the ETS  
project).

So, the upshot is that you can now do:

svn co https://svn.enthought.com/svn/enthought/aliases/trunk

and you will get the trunk directories for all of the projects in  
ETS.  You can do a single "svn up", and you will get updates across  
all of the projects.  You should also be able to do cross-project  
commits in a single transaction, but you will have to explicitly state  
the external directory names, like so:

   svn commit -m "blah blah" Chaco Enable Traits


-Peter
</description>
    <dc:creator>Peter Wang</dc:creator>
    <dc:date>2008-08-29T17:59:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16922">
    <title>Re: Installation difficulties (an understatement)</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16922</link>
    <description>Hi Kyle,

Kyle Walker wrote:

Sorry for the troubles you've been having!   I'm not an Ubuntu expert 
but my first thought is to ask if you've installed the basic development 
toolset on your machine?  You should be able to type 'gcc --help' in a 
terminal and have it display some usage.   If that works, passing on 
past a large set of assumptions now, can you tell me what version of 
numpy you have?


BTW: Unless there is some specific reason you want an older release of 
ETS, I would highly recommend you use the PyPi eggs like so:
    sudo easy_install --prefix=/usr/local ETS[nonets]

This will get you version 3.0.1 of ETS which is the latest release (as 
of today.)



Assuming you mean EPD 2.5.2001 for Windows there?  If so, sadly many of 
the examples provided by the Chaco project (and other projects) didn't 
work correctly in the ETS release in that EPD. :-(   This doesn't mean 
the rest of the install was bad though, but it is certainly 
understandable that it would make you feel that way.



Here at En</description>
    <dc:creator>Dave Peterson</dc:creator>
    <dc:date>2008-08-29T17:44:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16921">
    <title>Installation difficulties (an understatement)</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16921</link>
    <description>I am trying to install the latest version of ETS, and I just cannot
get it to go through.  I have tried Ubuntu 8.04 as instructed on the
wiki:

sudo apt-get install python-numpy python-scipy python-setuptools
python-vtk python-wxgtk2.8 python-pyrex
sudo easy_install -f
http://code.enthought.com/enstaller/eggs/ubuntu/hardy
--prefix=/usr/local ets

Which gives me this error:
  File "/usr/lib/python2.5/site-packages/numpy/distutils/ccompiler.py",
line 393, in &lt;module&gt;
    setattr(getattr(_m, _cc+'compiler'), 'gen_lib_options',
AttributeError: 'module' object has no attribute 'unixccompiler'


I could work through this error, but it is already about the 10th
problem I have had to deal with for this installation.  I have to be
missing something simple.

I tried to install from the svn, as well as from Gael's repository.  I
ran through the easy_install method real quick on Fedora 8 and my RHEL
5.1 machine at work.  Niether of those worked, but I didn't spend much
time trying to figure out why.  I installed the pyt</description>
    <dc:creator>Kyle Walker</dc:creator>
    <dc:date>2008-08-29T04:52:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16920">
    <title>Re: ArrayEditor string formatting?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16920</link>
    <description>
On Aug 27, 2008, at 11:48 AM, David C. Morrill wrote:

Thanks for the quick update.

--
Jed Frechette

University of New Mexico Lidar Lab
www.unm.edu/~lidar
</description>
    <dc:creator>Jed Frechette</dc:creator>
    <dc:date>2008-08-29T15:48:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16919">
    <title>Re: [mayavi] Help for standalone decorator script</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16919</link>
    <description>
On Aug 27, 2008, at 11:45 AM, Prabhu Ramachandran wrote:

Done, # 1667

Best,

--
Jed Frechette

University of New Mexico Lidar Lab
www.unm.edu/~lidar
</description>
    <dc:creator>Jed Frechette</dc:creator>
    <dc:date>2008-08-29T15:47:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16918">
    <title>Re: ETSConfig: addition of enable_toolkitcausesproblems</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16918</link>
    <description>Quoting Robin Macharg &lt;rmacharg-9eMfuE2pI0o&lt; at &gt;public.gmane.org&gt;:


Hey Robin,

You're right that the Enable.toolkit module should have a sensible  
default for each of the main ETS_TOOLKIT backends.  I'm actually  
working on that module a little bit right now so I can integrate  
Pyglet with wxPython, so I will take a look at this bug as well.

-Peter
</description>
    <dc:creator>Peter Wang</dc:creator>
    <dc:date>2008-08-29T13:44:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16917">
    <title>Re: Subtleties with NumPy requirement in Enable andChaco</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16917</link>
    <description>
Doh! User error! I build my eggs in build environment that I setup
with virtualenv (and install into a "clean" environment). I checkout
the ETS projects I use into a directory reflecting where I got it from
the repository (i.e. Trunk, 3.0.0, etc.) and then "bdist_egg -d
../eggs" in each project so that I get a directory layout like:

Trunk
    Traits
    Enable
    ...
    Chaco
    eggs

I then issued the command I gave at the prompt when I am in the Trunk
directory. Easy_install wasn't even looking in the eggs directory I
specified because there was a directory with the same name as the
project, so it tried to build it instead of just grabbing the egg.
Apologies for the noise!


This isn't a problem for me for the reason I mentioned above and now
that I discovered my issue was user error, my original bit of feedback
is moot. That said, I do use this ugly guarded require/import pattern
to support situations like this that I've had to deal with in my own
code:

try:
    import pkg_resources
    try:
       </description>
    <dc:creator>Alexander Michael</dc:creator>
    <dc:date>2008-08-29T12:50:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16916">
    <title>Filters for Contrib Directory</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16916</link>
    <description>Hi all,

I have been developing filters for the research group I have been 
working with, and today is my last with them.

I have attached some of the more general filters which I believe might 
be useful to some. They would certainly need some polishing if they are 
to be added to the trunk, but for now they can go into a contrib 
directory which has been suggested by Prabhu.

The filters are as follows:

* BoundaryMarkerEditor
Edit the boundary marker of a Triangle surface mesh. Use the 
TriangleReader which I have previously submitted to open such a mesh. To 
use this filter: select the label to assign, hover your cursor over the 
cell you wish to edit, and press 'p'.
Requires TriangleWriter to write changes to Triangle format files.

* MeshDiagnostics
Identifies stiff elements of a solid mesh (those elements whose points 
all lie on the surface). Also includes diagnostics from vtkMeshQuality:
&lt;http://www.vtk.org/doc/release/5.0/html/a01739.html&gt;

* TensorEigenvectorsEigenvalues
Computes the eigenvectors </description>
    <dc:creator>Daryl Harrison</dc:creator>
    <dc:date>2008-08-29T12:22:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16915">
    <title>Re: ETSConfig: addition of enable_toolkitcausesproblems</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16915</link>
    <description>
The 'it' in the above sentence should of course read 'our application'. ;-)

R
</description>
    <dc:creator>Robin Macharg</dc:creator>
    <dc:date>2008-08-29T11:14:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16914">
    <title>ETSConfig: addition of enable_toolkit causesproblems</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16914</link>
    <description>_______________________________________________
Enthought-dev mailing list
Enthought-dev-oRDGkvazHdacsI7C1d+pp9BPR1lH4CV8&lt; at &gt;public.gmane.org
https://mail.enthought.com/mailman/listinfo/enthought-dev
</description>
    <dc:creator>Robin Macharg</dc:creator>
    <dc:date>2008-08-29T10:50:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16913">
    <title>Re: Subtleties with NumPy requirement in Enable andChaco</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16913</link>
    <description>

This is during the build. Enable has always required numpy to build.
Since setup.py imports from numpy before any requirements get
processed, there isn't a good way to mark it as a dependency. Using
pkg_resources.require('numpy') is probably not going to happen; in
Python 2.4, it may not be installed with the .egg-info for setuptools
to find.

Sorry, you are going to have to activate the numpy egg before installing Enable.

</description>
    <dc:creator>Robert Kern</dc:creator>
    <dc:date>2008-08-29T06:00:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16912">
    <title>[Fwd: [vtk-developers] VTK 5.2.0]</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16912</link>
    <description>FYI.

cheers,
prabhu
_______________________________________________
Enthought-dev mailing list
Enthought-dev-oRDGkvazHdacsI7C1d+pp9BPR1lH4CV8&lt; at &gt;public.gmane.org
https://mail.enthought.com/mailman/listinfo/enthought-dev
</description>
    <dc:creator>Prabhu Ramachandran</dc:creator>
    <dc:date>2008-08-29T05:04:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.enthought.devel/16911">
    <title>ImageMarchingCube</title>
    <link>http://permalink.gmane.org/gmane.comp.python.enthought.devel/16911</link>
    <description>Hi,

I am trying to get the ImageMarchingCubes filter to work in Mayavi, and I
am being very stupid, and not figuring it out.

The test code I am using is:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
from numpy import *
from enthought.mayavi import mlab

x, y, z = ogrid[-10:10:100j, -10:10:100j, -10:10:100j]
s = x**2 + y**2 + z**2
sf = mlab.pipeline.scalar_field(s)
# This thing is poping up an UI, not good. Select ImageMarchingCube
mc = mlab.pipeline.user_defined(sf)
sur = mlab.pipeline.surface(mc)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

If anyone has an idea on how to make this filter work, I would be more
than happy.

Cheers,

Gaël
</description>
    <dc:creator>Gael Varoquaux</dc:creator>
    <dc:date>2008-08-29T02:14:30</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.python.enthought.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.enthought.devel</link>
  </textinput>
</rdf:RDF>
