On Fri, Oct 9, 2009 at 5:42 PM, Chris Withers <chris at simplistix.co.uk> wrote: > Tarek Ziadé wrote: >> >> - The code is splitted in many packages and might be distributed under >> several distributions. >> >> - distribute.resources: that's the old pkg_resources... > Why not just call it pkg_resources and/or merge it with pkgutil to get it > into the python stdlib? Because "pkg_resources" belongs to 0.6 and we want 0.7 to be installable alongside 0.6 if needed. Now as I said earlier, this package might shrink once PEP 376 is finished, and have bits included in pkgutil. > >> - distribute.entrypoints: that's the old pkg_resources entry points >> system, but on its own. it uses distribute.resources > > Why not get it into the core as distutils.entrypoints? That's where it > belongs... What do you call 'core' ? distutils.core ? If yes, why does it belong to core ? entrypoint is a standalon plugin system . > >> - distribute.index: that's package_index and a few other things. >> everything required to interact with PyPI. We will promote >> its usage and see if Pip wants to use it as a basis. > > Why not call in "pypi.client" and "pypi.server" or, better yet, get it into > the stdlib as disutils.index.client distutils.index.server? We are keeping a "distribute." namespace for all bits. Now maybe one day it'll make it into Distutils, yes. But not now. Also, have a look at PEP 381 (mirroring infratructure for PyPI) In any case, the splitting is occuring *now* and is not written in the stone, so we can talk about this in Distutils-SIG, and improve it with your feedback. Regards, Tarek
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4