Add project_urls metadata so tools can find the repository
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
The issue identifies pyproject.toml and gives the desired [project.urls] entries. Read the existing packaging metadata there, then check the built package metadata or PyPI JSON to confirm Homepage and Repository links are present and info.project_urls is no longer null.
Written by the indexing model from the issue text.
Description
The PyPI metadata for pluggy carries no project links:
- https://pypi.org/project/pluggy/ shows no Homepage / Repository links
- the JSON API returns
info.project_urls: nullandinfo.home_page: null
(https://pypi.org/pypi/pluggy/json)
So the source repository is undiscoverable from package metadata alone.
Tools that map a distribution back to its repo, dependency dashboards,
supply-chain/source audits, dataset builders, end up guessing or dropping
the package.
If you're happy to, adding [project.urls] to the packaging metadata fixes
this. With setuptools in pyproject.toml:
[project.urls]
Homepage = "https://github.com/pytest-dev/pluggy"
Repository = "https://github.com/pytest-dev/pluggy"
Checked against the current release (1.6.0); the rest of the metadata looks
fine.
Thanks!
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 172
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 21
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pytest-dev/pluggy
-
Plugin registry compares plugins by equality, not identityMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pytest-dev/pluggy#760 ·
Maintainers usually reply within 1 day
-
Defaulted positional-only hook parameters are forwarded as keywordsPossibly taken @adenzhou1350 claimed this today. Open
Difficulty 4/5 1-2 days Newbie friendliness 45/100
pytest-dev/pluggy#774 ·
Maintainers usually reply within 1 day
-
list_plugin_distinfo() keeps unregistered pluginsPossibly taken @RonnyPfannschmidt claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
pytest-dev/pluggy#763 ·
Maintainers usually reply within 1 day
-
unregister() argument validation relies on assertPossibly taken @ekanshul claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
pytest-dev/pluggy#762 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
pytest-dev/pluggy#761 ·
Maintainers usually reply within 1 day
All issues in pytest-dev/pluggy
Similar issues
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#136483 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
[BUG] LazyStackedTensorDictStore zeroes the last byte of a new key set on the last elementPossibly taken @peterdsharpe claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pytorch/tensordict#2307 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day