"Invalid constraint" message for package dependencies, but they are valid for pip
See original GitHub issue-
I am on the latest Poetry version.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option). -
OS version and name: Docker debian bullseye
-
Poetry version: 1.1.11
Issue
> poetry add markdown==3.3.5
Updating dependencies
Resolving dependencies... (0.0s)PackageInfo: Invalid constraint (importlib-metadata (>='4.4') ; python_version < "3.10") found in markdown-3.3.5 dependencies, skipping
Resolving dependencies... (0.1s)
Writing lock file
No dependencies to install or update
Full discussion on markdown package https://github.com/Python-Markdown/markdown/issues/1195, where they are saying that the versioning is correct and this is a Poetry problem. I’m no expert, but given it can install with pip, I think this likely is a Poetry issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Resolving new pip backtracking runtime issue - Stack Overflow
The behavior seen is described as backtracking in the release notes. I understand why it is there. It specifies that I can use...
Read more >Dependency Resolution - pip documentation v22.3.1
The process of determining which version of a dependency to install is known as dependency resolution. This behaviour can be disabled by passing...
Read more >FAQ | master | Documentation | Poetry - Python dependency ...
Why are unbound version constraints a bad idea? #. A version constraint without an upper bound such as * or >=3.4 will allow...
Read more >Installing Python dependencies - AWS Documentation
A Python dependency is any package or distribution that is not included in the Apache Airflow base install for your Apache Airflow version...
Read more >pip-tools - PyPI
Note : If pip-compile finds an existing requirements.txt file that fulfils the ... You declare django as a dependency and create an optional...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m getting the same issue here; same exact package.
However, I’ve gone a bit further here and found that
markdown==3.3.4
still works fine. I’m not sure if this is a severe poetry screw-up at this point with versioning, but I’m thinking that it’s amarkdown
issue, not apoetry
issue, based on the fact that 3.3.4 works fine and 3.3.5 doesn’t; they obviously changed versioning between these.Not to say that it’s not an issue in poetry, but, clearly the issue can be worked around as was < 3.3.5.
Resolved in
markdown
via https://github.com/Python-Markdown/markdown/pull/1197.