Re: [Distutils] [buildout] RFC: buildout support for distribute
At 09:53 PM 10/13/2009 +0200, Tarek Ziadé wrote:
2009/10/13 P.J. Eby <pje@telecommunity.com>:
At 09:25 PM 10/13/2009 +0200, Tarek Ziadé wrote:
Notice that the current trunk of Distribute is now changing any 'setuptools' requirement that is tiggered using "Requirement.parse" and "resolve" APIs into a 'distribute' one.
Please note that this change will cause problems for people in the future, as new features are introduced in the 0.7a1 line. The earlier version of this hack, which only ignored requests for older versions of setuptools, would not have caused such a problem.
I would suggest that Distribute should only silently ignore requests for versions of setuptools that it can explicitly emulate; other requests should result in an error, so that a problem cannot pass silently.
Otherwise, a package depending on new features in the 0.7 line will silently fail when those features are not present in its operating environment.
Ok sure, makes sense. We will return 'distribute' only if 'setuptools' is from the 0.6.x series and below.
Great. I assume that means you plan to incorporate any further bug fixes that land in 0.6c10 (or, gods forbid, c11) in the release where this change is made. For versions you don't support emulating, I strongly suggest adding an error of some kind, since actually *installing* setuptools with Distribute still present on sys.path would cause a problem.
On Tue, Oct 13, 2009 at 10:07 PM, P.J. Eby <pje@telecommunity.com> wrote:
Ok sure, makes sense. We will return 'distribute' only if 'setuptools' is from the 0.6.x series and below.
Great. I assume that means you plan to incorporate any further bug fixes that land in 0.6c10 (or, gods forbid, c11) in the release where this change is made.
Yes, as long as we are able to spot them in your commits / issue trackers changes. The latest commit you've made in setuptools package is still cryptic to us because it fixes many things at once. We were able to backport the sandbox violation but that's it at this point.
For versions you don't support emulating, I strongly suggest adding an error of some kind, since actually *installing* setuptools with Distribute still present on sys.path would cause a problem.
It is still unclear to me where this exception has to be thrown since some APIs in WorkingSet can be used just to check things out. I am guessing WorkingSet.resolve and parse_requirements are enough, but that's just from the zc.buildout use case.
participants (2)
-
P.J. Eby -
Tarek Ziadé