PEP 639, Round 3: Improving license clarity with better package metadata

Packaging Standards
106

After reading through the PEP again, I’m happy to say I conditionally accept it with one change!

For the change, I think consuming tools SHOULD reject invalid globs (h/t to @konstin for catching that). If @ksurma is okay with that change, I have a PR ready at PEP 639: Make the policy around globs tighter by befeleme · Pull Request #3913 · python/peps · GitHub . After that we can mark the PEP as conditionally accepted.

As for the conditions:

  1. Two build back-ends implement the PEP (which shouldn’t be too arduous since I know Hatch basically already does, so it’s really just one more)
  2. PyPI implements it (which will probably require packaging to gain some APIs around this like @pradyunsg volunteered us for :sweat_smile:)

Thanks so much to those who participated in the discussions, Philippe for the initial draft, @CAM-Gerlach for their updated version of the PEP, and @ksurma for reviving the PEP again and seeing it through to the end!

12 Likes