[Django] #18937: PEP 345
Django
-----------------------------+--------------------
Reporter: mjtamlyn | Owner: nobody
Type: New feature | Status: new
Component: Python 3 | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
Add a PKG-INFO file as fitting with
[http://www.python.org/dev/peps/pep-0345/ PEP 345].
See [http://blog.ziade.org/2012/09/10/dear-django-help-python-packaging/
this blog post] for reference.
Seems to me we can add this metadata file without too much difficulty and
make new packaging happy :D
--
Ticket URL: <https://code.djangoproject.com/ticket/18937>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-----------------------------+------------------------------------
Type: New feature | Status: new
Component: Python 3 | Version: master
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 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
Type: New feature | Status: new
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Changes (by jezdez):
* component: Python 3 => Core (Other)
--
Ticket URL: <https://code.djangoproject.com/ticket/18937#comment:2>
Django
Reporter: mjtamlyn | Owner: nobody
Type: New feature | Status: new
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by timgraham):
Is this ticket still important 3 years later? If so, how can we move it
forward?
Just to clarify, the complaint is that our `PKG-INFO` file uses "Metadata-
Version: 1.1" instead of "1.2"?
--
Ticket URL: <https://code.djangoproject.com/ticket/18937#comment:4>
Django
-----------------------------+------------------------------------
Type: New feature | Status: closed
Component: Packaging | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => fixed
Comment:
So 5 years later this ticket is no longer applicable.
* The original blog post linked suggested moving to Setuptools as a
possible option. This was done in
[https://github.com/django/django/commit/66f546b90624297858b0f958abbe5c2b3e8bdffb
66f546b906].
* Setuptools handles
[https://github.com/pypa/setuptools/blob/d10a1bb476db25dc888b5b4aad9d81ffa245ea30/setuptools/dist.py#L39-L48
writing the PKG-INFO file, including version 1.2 metadata]
* The generated `PKG-INFO` file **does** use `Metadata-Version: 1.2`:
{{{
Metadata-Version: 1.2
Name: Django
Version: 2.1.dev20180208153510
...
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18937#comment:5>