-
Notifications
You must be signed in to change notification settings - Fork 10
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
Broken dependency for python 3.12 #134
Comments
Hi, thanks for reporting. I presume this was produced with I am not able to reproduce this behavior with python 3.12, neither with |
We discovered this bug across two machines here, testing with both 3.9 and 3.12. Seems like [project]
name = "testqats"
version = "0.1.0"
description = ""
authors = []
readme = "README.md"
requires-python = ">=3.10,<3.13"
[build-system]
requires = ["poetry-core>=2.0.0,<3.0.0"]
build-backend = "poetry.core.masonry.api"
then running
Reproduces the error message: |
When i try to pip install shiboken6, pip only finds shiboken 6.8.1. Not 6.8.8.1 as required. Seems like windows wheels are missing from shiboken 6.8.8.1, as this is the only one distributed:
|
As far as I understand, this is caused by On the good side; rerunning the tests for python 3.12 on PR #133, |
Update: shiboken6 version 6.6.x doesn't seem to work well with numpy version 2.x. Allowing for pyside6 version 6.8 is therefore desirable. The following dependency, which avoids version 6.8.1.1 of pyside6 and shiboken6, seems to work well: A looser dependency, allowing for |
Thanks for following up. Locking the dependency to 6.8.1 on our side is a ok workaround for now. |
Describe the bug
New release of pyside6 breaks dependencies. To fix it I locked pyside6 to 6.6.0
To Reproduce
When installing latest QATS on python 3.12:
I get the following error:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: