You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed it works for flit build. But it fails for flit publish:
requests.exceptions.HTTPError: 400 Client Error: Invalid value for requires_dist. Error: Can't have direct dependency: 'a_repo_pkgname @ git+https://github.com/a_project/a_repo.git' for url: https://upload.pypi.org/legacy/
It seems to be the policy of PyPI to reject dependencies that are code repositories. Have a look at this.
Nothing to do with flit, as far as I can understand.
The only relevant thing is: flit displayed a python traceback when trying to publish.
Phenomena
Migrating from
requirements.txt
to
pyproject.toml
and using Flit:With the above illustrated
pyproject.toml
,flit build
results in error reading:$ flit build Could not parse requirement: 'git+https://github.com/a_project/a_repo.git' E-flit.validate Config error: Invalid config values (see log)
Expected Behavior
Expects dependency installation works, being consistent with
pip
install from arequirements.txt
.Reference
pip install
dependencies from VCSThe text was updated successfully, but these errors were encountered: