On Tue, Jul 17, 2007 at 04:54:49PM -1000, Eric Firing wrote:
> The 2.0 branch is not new enough, though; we need the trunk.  

Nonononono. Believe me. Unless you want to live on the bleeding edge. All
the QA is done on the branches. The trunk is for active developement
(some active developement happens in the branches, like for mayavi2, so
far). It is not even garantied to work (it does, most of the time).

> (I tried the 2.0 branch, but it turned out to depend on enthought.util,
> which depended on enthought.somethingelse... so I stopped.  Also it was
> using numerix; it is not numpified.)

Traits depend on enthought.etsconfig and enthought.util. Once traits is
on pypi, these dependencies should install automatically. I am wondering
if there is a possibility of shipping a "fat" egg, that provides the
dependancies, just in case the user does not have internet access, and
that first checks pypi before using the local dependencies.

I am very surprised about the comment on traits numpification. I just
tried out my local copy, and it is clearly numpified. I didn't do
anything special to instal it, just built from source. What makes you
think the branches are not numpified ?

Cheers,

Gaƫl

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to