On Wed, Jan 26, 2011 at 3:36 AM, Brian Jones <[email protected]> wrote: ... >> http://mail.python.org/pipermail/catalog-sig/2010-September/003301.html > > I'm not positive we're on the same page. You seem to be talking about adding > some specific new data in a specific way to the index, and *then* making it > available. I'm talking about making the *current* data available to programs > the same way it's available via a web interface. It seems your ideas were > shot down because "it's coming", if I read it right. I myself am kind of > confused about that, because my understanding is also that "it's coming" in > the form of a tool that can only be used for Python 3 packages :/
No, the tool will be usable by python2 packages as well. I don't want to do that thread again but basically, egg_info are platform-specific, whereas the new metadata version (PEP 345) will have them right. PyPI already supports PEP 345. .. >> >> Please be prepared that any changes to this feature likely get shot >> down, also. > > Thanks for the heads up. > >> >> If it doesn't get shot down, we can >> ponder implementing it, in which case contributions would be welcome. > > You'd do that for me? > Thanks, I would not use the word "get shot down", that is scary for people that want to contribute here. I'd rather say "get a consensus on a feature before implementing it", because that's really what it is. -- Tarek Ziadé | http://ziade.org _______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
