This is a bugfix release to fix a few issues with 0.6b1. Please upgrade and test if you can, I'd like to release an 0.6 final soon. There are still a couple of known minor issues that I haven't addressed yet (error messages from ez_setup/easy_isntall reported here by Nathan Yergler), but I wanted to get this intermediate release out because of one serious bug that affects you if you install a package whose name begins with the word "import" on Windows -- e.g., my own "Importing" package, published recently on PyPI.
Anyway, the next release of 0.6 should be a release candidate, so please beat on this one hard to find any remaining bugs. I'd like to get started on 0.7 (and the "nest" tool suite) as soon as practical.
(By the way: setuptools 0.6 is probably not going in the 2.5 stdlib; after lots of discussion on Python-Dev, it's fairly clear that some 0.7 release should be the earliest version to go in, once the "nest" tools are done. Practically speaking, that probably means waiting until Python 2.6, due to the lead time that would be needed to get adequate field testing of the "nest" tools once they're written.)
On 6/1/06, Phillip J. Eby pje@telecommunity.com wrote:
(By the way: setuptools 0.6 is probably not going in the 2.5 stdlib; after lots of discussion on Python-Dev, it's fairly clear that some 0.7 release should be the earliest version to go in, once the "nest" tools are done. Practically speaking, that probably means waiting until Python 2.6, due to the lead time that would be needed to get adequate field testing of the "nest" tools once they're written.)
That's unfortunate, though I can certainly understand the rationale. Based on feedback I've seen on the TG list, ability to easily manage eggs is a fairly common desire.
Kevin
On Thu, 1 Jun 2006, Kevin Dangoor wrote:
On 6/1/06, Phillip J. Eby pje@telecommunity.com wrote:
(By the way: setuptools 0.6 is probably not going in the 2.5 stdlib; after lots of discussion on Python-Dev, it's fairly clear that some 0.7 release should be the earliest version to go in, once the "nest" tools are done. Practically speaking, that probably means waiting until Python 2.6, due to the lead time that would be needed to get adequate field testing of the "nest" tools once they're written.)
That's unfortunate, though I can certainly understand the rationale. Based on feedback I've seen on the TG list, ability to easily manage eggs is a fairly common desire.
Heh -- that may have been part of the rationale, but it wasn't the cause. Several core Pythonistas objected in strong terms on python-dev to various aspects of it. Still, Guido clearly wants it, so seems pretty sure thing for 2.6 still.
No doubt PJE made the decision to pull it for a combination of reasons, though.
Best of luck with TG
John
[...]
Heh -- that may have been part of the rationale, but it wasn't the cause. Several core Pythonistas objected in strong terms on python-dev to various
[...]
Oh sugar, didn't mean to post that, and risk stiring this up again, yawn (I only meant to email it to KD).
Please ignore
John
At 08:16 PM 6/1/2006 +0000, John J Lee wrote:
Heh -- that may have been part of the rationale, but it wasn't the cause. Several core Pythonistas objected in strong terms on python-dev to various aspects of it.
Actually, three people objected, and one of them actually had some good points that led me to pull back. Fredrik raised the issue of support, especially with respect to the sometimes confusing and baroque command-line interface to easy_install. I agree that it's not reasonable to expect the core Python team to support all its intricacies at the present time.
Still, Guido clearly wants it,
It was only on the table because of Guido's request in the first place; in a private email I originally told him I wasn't sure about doing an 0.6 unless it could be upgraded on-the-fly (which it can, now) but I wasn't 100% sure anyway. The support issues, the short timeline, and lack of volunteers basically sealed its fate for 2.5, though.
participants (3)
-
John J Lee -
Kevin Dangoor -
Phillip J. Eby