-
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
AttributeError : EmptyConstraint object has no attribute allows #4398
Comments
Can you run |
Sure, here is the full stacktrace (for python3.9 this time)
|
This looks like something that appeared today - all my builds (in Docker) are now failing with the exact same error. Those worked last week. I even tried the new Edit: it was |
I wonder if a single package was pushed to PyPi with an empty constraint and we all happen to reference it? I'm working through the dependencies for our project now |
the problem seems to be with the newest |
From inspecting the object with the EmptyMarker:
And inspecting my lockfile:
I have a hunch the issue might be the |
Seems to be an issue with SQLAlchemy 1.4.23 that was released ~3 hours ago. Can someone open an issue with them if not already? After work, I can submit an issue otherwise A temporary workaround is pinning to 1.4.22 ( |
hey there - this is a poetry issue. SQLAlchemy is using https://www.python.org/dev/peps/pep-0508/ specifiers and as far as we can tell, the syntax is valid. There is no issue with our software installing with pip. |
This is a bug. Is a very obvious bug for 1.1.7. The EmptyConstraint class does not implement the allows method. Just implementing it to return True appeared to fix it in my case, though I'm not clear entirely clear if a blanket True is the correct behaviour. |
On closer inspection, I'm not sure whether this issue should be raised in poetry core? It does appear the bug exists on master (https://github.com/python-poetry/poetry-core/blob/5812d6db7ae95ac0dd11b498e47f3c3f17a27857/poetry/core/packages/constraints/empty_constraint.py#L10) |
Does anyone know if the contribution rules for poetry-core are the same as poetry? I'm happy to try and propose a fix, but want to make sure I'm following the correct procedure. |
Put up python-poetry/poetry-core#187. Hopefully it's correct, and fixes this issue. |
This seems to be fixed in poetry 1.1.8. |
Am closing the ticket as it was resolved. Thank you all. |
Given #4429 and the fact that this error is in poetry-core, can one of the maintainers comment whether upgrading poetry-core>=1.0.4 is the better fix? |
this issue/bug still exists for poetry 1.2.0a2, i think need to be reopened. or the changes 1.1.8 has needs to be imported into 1.2.0a2 if missing |
No, the fix was made in poetry-core. In the 1.0 branch and the master branch. There was a release 1.0.4 which is used by poetry 1.1.8. But the poetry preview release still uses poetry-core 1.1.0a6. I think with the next preview release of poetry, there will be also a new release for poetry-core which then contains the fix.. |
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. |
-vvv
option).Issue
Tried both with python3.8 and python3.9 resulting in this same error.
The text was updated successfully, but these errors were encountered: