Their official thinking is to stick to it, and to improve it. But I have
started release tarball that require setuptools only to build, but not at
run-time. They are being used to package traits, traitsUI and mayavi2 in
Debian. I would be happy to guive more info about that, but I am
currently travelling, and my internet access is very poor.
Beta versions of tarballs are on
http://code.enthought.com/downloads/source . I will make cleaner tarballs
of the release that was done last week when I get back home. These
tarballscan be used for eg packaging, or integrating the dependency, as
Fernando does in ipython.
Cheers,
Gael
···
On Wed, Oct 31, 2007 at 11:49:24AM -0400, Darren Dale wrote:
> On Mon, Oct 29, 2007 at 12:05:25PM -1000, Eric Firing wrote:
>> When I go to the enthought web site, the most recent traits release I
>> see is 1.1, from August 2006. That doesn't make me optimistic about
>> traits as an external dependency any time soon.
> That's because the website is unmaintained. There have been two releases
> lately. One during scipy, and one mainly bug fix and small improvements,
> last week.
> This shows that enthought is really bad at communicating there work,
> something that I have come to realize, and that is a major prolblem.
> The software it self is pretty good, it just lacks packaging (I have more
> and more doubts about eggs), good release plans, and testing with
> different uses than enthought's.
During the last Scipy conference, Fernando Perez and (I think) Dave
Peterson tracked down the source of a performance hit when we use our new
config package, which uses traits. They determined it was an issue with
setuptools. Do you know what is enthought's current thinking about using
setuptools?
This is just what we are looking for. Please let me know when the new tarballs
are available.
Darren
···
On Wednesday 31 October 2007 12:07:12 pm Gael Varoquaux wrote:
On Wed, Oct 31, 2007 at 11:49:24AM -0400, Darren Dale wrote:
> > On Mon, Oct 29, 2007 at 12:05:25PM -1000, Eric Firing wrote:
> >> When I go to the enthought web site, the most recent traits release I
> >> see is 1.1, from August 2006. That doesn't make me optimistic about
> >> traits as an external dependency any time soon.
> >
> > That's because the website is unmaintained. There have been two
> > releases lately. One during scipy, and one mainly bug fix and small
> > improvements, last week.
> >
> > This shows that enthought is really bad at communicating there work,
> > something that I have come to realize, and that is a major prolblem.
> >
> > The software it self is pretty good, it just lacks packaging (I have
> > more and more doubts about eggs), good release plans, and testing with
> > different uses than enthought's.
>
> During the last Scipy conference, Fernando Perez and (I think) Dave
> Peterson tracked down the source of a performance hit when we use our new
> config package, which uses traits. They determined it was an issue with
> setuptools. Do you know what is enthought's current thinking about using
> setuptools?
Their official thinking is to stick to it, and to improve it. But I have
started release tarball that require setuptools only to build, but not at
run-time. They are being used to package traits, traitsUI and mayavi2 in
Debian. I would be happy to guive more info about that, but I am
currently travelling, and my internet access is very poor.
Beta versions of tarballs are on
http://code.enthought.com/downloads/source . I will make cleaner tarballs
of the release that was done last week when I get back home. These
tarballscan be used for eg packaging, or integrating the dependency, as
Fernando does in ipython.
I forgot to let you know :->.
I made a new release on Saturday. Its a traits 2 release, not a traits 3,
but eventhough this is not the latest and greatest, this is what I use on
a day to day basis, and it is a well tested and solid release.
Ga�l
···
On Wed, Oct 31, 2007 at 01:55:09PM -0400, Darren Dale wrote:
> Beta versions of tarballs are on
> http://code.enthought.com/downloads/source . I will make cleaner tarballs
> of the release that was done last week when I get back home. These
> tarballscan be used for eg packaging, or integrating the dependency, as
> Fernando does in ipython.
This is just what we are looking for. Please let me know when the new
tarballs are available.