PyPI release failing due to direct git dependency
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, python
- Domain
- build-system, release
Research direction
Start with the linked release log and trace the packaging configuration that declares grimoirelab-toolkit as a direct git dependency. Done when the package can be uploaded to PyPI without the 400 direct-dependency error.
Written by the indexing model from the issue text.
Description
<html>
<head>
<title>
400 Can't have direct dependency: grimoirelab-toolkit @
git+https://github.com/chaoss/grimoirelab-toolkit.git. See
https://packaging.python.org/specifications/core-metadata for more information.
</title>
</head>
<body>
<h1>
400 Can't have direct dependency: grimoirelab-toolkit @
git+https://github.com/chaoss/grimoirelab-toolkit.git. See
https://packaging.python.org/specifications/core-metadata for more information.
</h1>
The server could not comply with the request since it is either malformed or otherwise incorrect.<br /><br />
Can't have direct dependency: grimoirelab-toolkit @ git+https://github.com/chaoss/grimoirelab-toolkit.git.
See https://packaging.python.org/specifications/core-metadata for more information.
</body>
</html>
ERROR HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
Bad Request
Release log: https://github.com/aboutcode-org/healthycode/actions/runs/35199480396/job/105130638325
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 4
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 aboutcode-org/healthycode
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aboutcode-org/healthycode#23 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aboutcode-org/healthycode#19 · 1 comment ·
-
clean up repoMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aboutcode-org/healthycode#33 · 1 comment ·
-
healthycode: Document HealthyCode Deployment sizing parameters (Compute/Memory/Storage)Possibly taken @d4rshnn claimed this 10 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
aboutcode-org/healthycode#26 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
aboutcode-org/healthycode#25 ·
All issues in aboutcode-org/healthycode
Similar issues
-
bug Frontend Medium Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Web3Novalabs/Nevo#1733 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
kenzok8/openwrt-honk#35 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day