#18937: Use modern Python packaging metadata standard (1.2, PEP 345)
-----------------------------+------------------------------------
Reporter: mjtamlyn | Owner: nobody
Type: New feature | Status: new
Component: Python 3 | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by jezdez):
* needs_better_patch: => 0
* needs_docs: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
Comment:
FWIW, PEP345 is just the metadata standard, not really the carrier of the
data. But it's easy enough to put the info in a setup.cfg as it's
implemented by distutils2/packaging
(http://alexis.notmyidea.org/distutils2/setupcfg.html).
We could use wrappers like d2to1 (http://pypi.python.org/pypi/d2to1) to
maintain only one file with the data but would still be forward-
compatible.
On the other hand as long as distutils2/packaging isn't officiall
released/included in Python 3.X it may be senseless to do so.
--
Ticket URL: <https://code.djangoproject.com/ticket/18937#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
