-
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
Unable to add debugpy
as a dependency
#7686
Comments
First of all, the debugpy wheel is invalid and you should raise an issue there. However, considering the early feedback after 1.4.1 (not just here but also on our Discord server), there might be more invalid wheels out there than we thought so we might turn the error into a warning in another patch release. Workaround for now: set |
debugpy is an indirect dependency of this project. When poetry 1.4.1 is used with the default configration, poetry refuses to install debugpy, due to recognizing something wrong with the wheel. This is the same issue (with the same dependency) as: python-poetry/poetry#7686 For now, I'm setting installer.modern-installation to false, per the workaround in: python-poetry/poetry#7686 (comment)
I'd hold firm! The reasoning of #7671 is still true: failing to install these packages is correct behaviour, users should report broken packages to the maintainers of those packages, they can use the non-modern installer if they need a workaround. Looking at it another way: this failure already serves as a warning, which can be worked around - it's a much more effective warning than some text that everyone will ignore will ever be. (I suspect this view is likely to be overruled, but I want it out there) Edit: perhaps a sensible halfway house would be: fail by default, require users to pass a flag to reduce the failure to a warning. |
debugpy is an indirect dependency of this project. When poetry 1.4.1 is used with the default configration, poetry refuses to install debugpy, due to recognizing something wrong with the wheel. This is the same issue (with the same dependency) as: python-poetry/poetry#7686 For now, I'm setting installer.modern-installation to false, per the workaround in: python-poetry/poetry#7686 (comment)
This is python-poetry/poetry#7686. Same workaround as EliahKagan/palgoviz#88 (python-poetry/poetry#7686 (comment)).
This is python-poetry/poetry#7686. Same workaround as EliahKagan/palgoviz#88 (python-poetry/poetry#7686 (comment)).
@radoering , @dimbleby , thank you both for the quick responses. At your direction, I have created microsoft/debugpy#1246 in the upstream repo. If there is any additional context about this issue that's worth providing the maintainers of that repo, I'd appreciate you providing it 🙏 I trust your judgement if you prefer to close this issue now that that one has been opened. |
This lets poetry install debugpy. See: - python-poetry/poetry#7686 - python-poetry/poetry#7686 (comment) - EliahKagan/palgoviz#88 - EliahKagan/findrepo2-experiment#55
This caused an issue when running the test suite, which could involve creating multiple hundreds of context, ultimately leading to a crash (see moderngl/moderngl#575) Also excluded poetry 1.4.1 from CI, see python-poetry/poetry#7686 and pradyunsg/furo#639
this seems like a reasonable compromise to me. Currently lots of packages have started failing installation due to a point upgrade of poetry |
Yup, the easiest thing for me and my team is to use poetry 1.4.0, so that's what we're doing. We can't wait for these packages to figure it out. |
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
As of Poetry v1.4.1, packages were required to use modern installation (see: python-poetry/poetry#7686). This is potentially problematic when relying on older versions of packages and for packages who are still using non-modern installers. This commit adds an additional step to disable that modern-installation requirement, which should get the workflow working again.
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. |
OS version and name: Arch Linux 6.2.6-arch1-1
pyproject.toml: pyproject.toml
I am on the latest stable Poetry version, installed using a recommended method. pipx
I have searched the issues of this repo and believe that this is not a duplicate.
I have consulted the FAQ and blog for any relevant entries or release notes.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option) and have included the output below.Issue
Adding
debugpy
fails for Python 3.11 (debug output printed below). I discovered this while trying to installjupyterlab
/ipykernel
which havedebugpy
as a dependency.I am filing the issue with poetry because I am able to install
debugpy
usingpip
.The text was updated successfully, but these errors were encountered: