Opened 4 years ago

Last modified 9 months ago

#18937 new New feature

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

Reported by: mjtamlyn 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 (4)

comment:1 Changed 4 years ago by jezdez

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Summary changed from PEP 345 to Use modern Python packaging metadata standard (1.2, PEP 345)
  • Triage Stage changed from Unreviewed to Accepted

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 4 years ago by jezdez

  • Component changed from Python 3 to Core (Other)

comment:3 Changed 3 years ago by aaugustin

  • Component changed from Core (Other) to Packaging

comment:4 Changed 9 months ago 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"?

Note: See TracTickets for help on using tickets.
Back to Top