PyPI release failing due to direct git dependency

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

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

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&#x27;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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/healthycode

All issues in aboutcode-org/healthycode

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.