-
Notifications
You must be signed in to change notification settings - Fork 4
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
After porting to pyproject.toml, rst.linker fails with error in Sphinx #17
Comments
The key that's causing the issue is |
Creating an empty |
Creating a
Removing one of those keys but leaving others produces different obscure errors, suggesting the issue might actually be in jaraco.packaging. |
Indeed, removing jaraco.packaging and the things that rely on it also bypasses the issue, so the issue must be there. |
It seems that |
Aha. So switching from setup.cfg to pyproject.toml has changed the metadata.
|
Man, core metadata is a mess. There's no obvious place to find the author's name nor the project URL. If I want to get a URL suitable for setting "package_url", I can't, because every URL is keyed on free-text that any package author could supply (or not). |
Half of the problem is described at pypa/packaging-problems#606. It hints that Setuptools might auto-convert some URLs, but that's apparently not the case. The work in python/cpython#108580 would help here to have some re-usable ways to parse author/maintainer fields. |
In https://github.com/jaraco/tempora/actions/runs/8714844379/job/23905742259, the docs build is failing and it implicates rst.linker. Passing -v to the sphinx build provides more context:
The text was updated successfully, but these errors were encountered: