Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Json Information for package pyparsing on PyPi is incomplete #422

Open
fer-rum opened this issue Jun 29, 2022 · 3 comments
Open

Json Information for package pyparsing on PyPi is incomplete #422

fer-rum opened this issue Jun 29, 2022 · 3 comments

Comments

@fer-rum
Copy link

fer-rum commented Jun 29, 2022

The file in question is https://pypi.org/pypi/pyparsing/3.0.9/json

image

Basic information like the license are not given properly (although it appears on the pypi website for pyparsing ).

@ptmcg
Copy link
Member

ptmcg commented Jun 30, 2022

Thanks for pointing me to this, I am new to using pyproject.toml (which is where it looks like much of this metadata comes from).

I'm reading this page (https://packaging.python.org/en/latest/specifications/declaring-project-metadata/) for guidance, and it seems that many of these fields should be defined, based on content in pyproject.toml. I'm reluctant to add undocumented fields, given that uploading to pypi is essentially a you-only-get-one-shot-to-upload-your-version-so-get-it-right-on-the-first-try interface.

I see that there are some classifiers that need to be added, which I have done and committed to the master branch. But if there are additional fields that you can provide in a tested PR, they would be welcome.

@fer-rum
Copy link
Author

fer-rum commented Jun 30, 2022

According to what I see in the pyproject.toml it should work. In our own project we forgo the [project]-section completely and specify everything in the [tools.poetry] section which produces the desired JSON. I see two possible reasons here:

  1. We are missing something obvious
  2. Something is off with the release procedure for pypi (Something configured wrong? Missed steps? Innocent Typo?)

@MiWeiss
Copy link

MiWeiss commented Jul 9, 2022

I'm reluctant to add undocumented fields, given that uploading to pypi is essentially a you-only-get-one-shot-to-upload-your-version-so-get-it-right-on-the-first-try interface.

Maybe test.pypi.org can help?

It's not perfect (for example, you also can't delete releases), but at least a wrong release does not pollute the (main) pypi index. I sometimes use it to test-deploy RCs exactly when I have concerns about metadata etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants