-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version Parse error #4095
Comments
I'm seeing the same issue with |
Is $ curl -sL https://pypi.org/pypi/aio-pika/json | jq -r .info.requires_python
>3.5.*, <4 Seems PEP 345 Requires-Python section indicates that the value must be a valid Version Specifiers. This inturn expects this to be PEP 440. Which this is not afaict. EIther poetry needs to relax the checks (which might cause unintended side-effects) or the project should use |
I'm not very familiar with the version PEPs, but it seems excluding versions is very frequent, for example
so one would expect other inequalities would also be allowed. I can open an issue for the |
I don't think the |
Closing this, because it's not poetry issue. (Hopefully they will fix it upstream, because I'm using this packages as well) |
@finswimmer can we consider maybe adding an ignore flag ? or being less strict with a warning period? This change is ofc good but it causes real issues that restricts many developers from updating to the new poetry version. |
@finswimmer - seconding the above comment. While being more strict with versioning is great for the entirety of the python community, it is going to make the new release of poetry unusable in many circumstances as some python packages will become unusable. I ran into this issue with Poetry should try to make an assumption in cases like this but log a waning about potential issues. Ideally, it would also provide a link to get more info about what is incorrect, why its incorrect, and how to fix it so that poetry users can submit PRs to slowly resolve these issue across the board. Something that I would like to see in the next prerelease of poetry (if it has not been done already) is a better error when this issue is encountered. Right now, if I start using poetry 1.2.0a1 after using 1.1.6, it will result in the |
According to PEP 345 Requires-Python (https://www.python.org/dev/peps/pep-0345/#requires-python), the value of this field must be a valid Version Specifier (https://www.python.org/dev/peps/pep-0345/#version-specifiers). Which in turn expects this to comply with PEP 440 (https://www.python.org/dev/peps/pep-0440/). While not an issue for those that directly use `pip`, this will cause issues for `poetry` users in the next release (if their current stance is maintained). Discussion of the issue and there stance can be found here: python-poetry/poetry#4095.
Created a new issue for this as it seems unanswered here #4176 . |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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: All Platforms
Poetry version: 1.2.1a
Issue
Python constraints issues happens when installing aiopika with weird python specifications -
poetry add aiopika
The text was updated successfully, but these errors were encountered: