-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Update PyPi package registry to use project.urls from pyproject.toml #33085
Comments
If it is the case that we are using deprecated metadata to get the home page URL (to me this looks to be the case), then I agree that we should use something else to get this URL. What we should do is:
|
I'll see if I can implement something like this today |
Hi guys, thanks for getting this implemented so quickly! Not an urgent one, but would there be interest in the future in adding links for other project URLs too similar to pypi? |
Please create a new issue so that it can be found by contributors. |
Description
At the moment a link only seems to appear in the pypi package registry for setup.cfg files with a url field, which is translated to a Home-page metadata field. I believe this bit of meta-data has been deprecated recently: https://packaging.python.org/en/latest/specifications/core-metadata/#home-page
I believe the issue may be related to this line (but not fully sure):
gitea/routers/api/packages/pypi/pypi.go
Line 142 in 9882917
Ideally links would appear in a similar way to that in pypi (Where the [project.urls] table can take homepage, documentation, tracker etc.)
The current documentation on what metadata is available and how it is used could also be heavily improved.
Gitea Version
1.21.11
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Windows Server
How are you running Gitea?
Running the .exe on a Windows Server
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: