It's nice to have that split up into lots of more focused documents. The comment I have is that I think entry points sometimes have multiple values with the same name (a list or multidict instead of a simple dict) although I'm not sure how common that is...
Tools should just do automatic conversion of entry_points.txt to the new metadata format when .dist-info is in use. On Tue, Dec 31, 2013 at 3:05 PM, Marcus Smith <qwc...@gmail.com> wrote: > ok, so PEP459 has exports: > http://www.python.org/dev/peps/pep-0459/#the-exports-extension > and distlib seems to be implementing them. > > and "exports" seem to be entry points 2.0. > > so theoretically, when PEP426/PEP459 becomes live.... > > what does that mean for setuptools-based projects? (I understand that we > might not have a clear idea now, but just trying to narrow down the > possibilities) > > 1) the setuptools "entry_points" keyword (and pkg_resources api) gets > re-implemented to understand PEP459 exports? > or > 2) "entry_points" keeps the old implementation, and possibly tools are > written to handle the old and new metadata? > or > 3) "entry_points" are stranded, and consumers have to rewrite setup.py files > to use some new keyword that understands PEP459 > or > 4) something altogether different... > > as for why I'm asking, pip itself is considering command extensions, so it's > a direct practical matter for us. > > Marcus > > > > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
