Opened 6 years ago

Closed 8 months ago

#18937 closed New feature (fixed)

Use modern Python packaging metadata standard (1.2, PEP 345)

Reported by: Marc Tamlyn Owned by: nobody
Component: Packaging Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Add a PKG-INFO file as fitting with PEP 345.

See this blog post for reference.

Seems to me we can add this metadata file without too much difficulty and make new packaging happy :D

Change History (5)

comment:1 Changed 6 years ago by Jannis Leidel

Summary: PEP 345Use modern Python packaging metadata standard (1.2, PEP 345)
Triage Stage: UnreviewedAccepted

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 (

We could use wrappers like 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.

comment:2 Changed 6 years ago by Jannis Leidel

Component: Python 3Core (Other)

comment:3 Changed 6 years ago by Aymeric Augustin

Component: Core (Other)Packaging

comment:4 Changed 3 years ago by Tim Graham

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"?

comment:5 Changed 8 months ago by Carlton Gibson

Resolution: fixed
Status: newclosed

So 5 years later this ticket is no longer applicable.

Metadata-Version: 1.2
Name: Django
Version: 2.1.dev20180208153510
Note: See TracTickets for help on using tickets.
Back to Top