Consider renaming this project to not include the PEP number

[pradyunsg]

We've already made this mistake once with pep517 and I'd really like it if we as a community can avoid doing that again with this project.

pep517 is realistically a package for providing wrappers for hooks that were initially specified in PEP 517. Those have since been expanded, most recently in PEP 660 and now the project name does not make as much sense. We also made the same mistake in pip's CLI -- using the PEP name rather than a user-friendly concept name.

Let's use a more user-friendly name here, that better conveys the purpose of this package?

[FFY00]

That makes sense, what name do you propose?

When I released this, I did not intend it to be a round for a long time, as I hope this functionality will eventually be provided by https://github.com/pypa/packaging. I just created this package because I was developing a few different build backends and wanted to reuse the code, so I just extracted it to a separate package.
I am fine keeping supporting this, but I hope https://github.com/pypa/packaging will provide metadata handling soon(-ish).

[pradyunsg]

https://pypi.org/project/pyproject-metadata?

[FFY00]

@pradyunsg that sounds good. Could you either delete the PyPI project or add me as a maintainer?

[pradyunsg]

You should've gotten an invite. :)

[FFY00]

@pradyunsg I don't think I ever got an invite. I would like to make a release soon, could you look into that?

[pradyunsg]

I’d certainly sent an invite, which the PyPI UI states had expired. Sent another invite!

[pradyunsg]

There’s a 24 hour expiry on the invite, IIRC.

[FFY00]

Pushed a 0.5.0 release under the new name. @pradyunsg many thanks.