We are getting along fine too. No tool parses metadata 1.x for package management reasons and provides has existed forever with no implementation. So it is not inconveniencing anyone. I would prefer to leave it alone.
Daniel Holth On Nov 19, 2012, at 7:49 PM, Donald Stufft <[email protected]> wrote: > Other languages seem to get along fine without it. Even the OS > managers which have it don't allow it to be used to masquerade > as another project, only to make generic virtual packages (e.g. "email"). > On Monday, November 19, 2012 at 7:43 PM, Daniel Holth wrote: > >> Does it really have baggage? I think it is necessary, although it doesn't do >> favors to the implementer (and has never been implemented). How else is >> anyone supposed to fork or merge projects? >> >> Daniel Holth >> >> On Nov 19, 2012, at 7:37 PM, PJ Eby <[email protected]> wrote: >> >>> On Mon, Nov 19, 2012 at 6:53 PM, Daniel Holth <[email protected]> wrote: >>>> I think this PEP is a significant improvement from its predecessor. It >>>> represents features like extras (provides-extra) and build requirements >>>> (setup-requires-dist) that are in use in the Python community but cannot >>>> be represented in older versions of the format, it finally specifies a >>>> UTF-8 encoding, removes RFC 822, provides an extension mechanism, and >>>> allows the description to be placed in the document payload. >>> >>> Can we maybe kill Provides-Dist and its associated baggage first, though? >>> >> >> _______________________________________________ >> Python-Dev mailing list >> [email protected] >> http://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> http://mail.python.org/mailman/options/python-dev/donald.stufft%40gmail.com >
_______________________________________________ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
