-
-
Notifications
You must be signed in to change notification settings - Fork 8.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
[🐛 Bug]: PyPI: selenium 4.17.0 whl is not defining strong version requirement to typing-extensions #13488
Comments
@rpysz, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Duplicate of #13486 |
@diemol Do you plan to release a revised version of wheel file on PyPI in the near future? |
After the PR that fixes the issue is merged, I will do a release. |
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. |
What happened?
https://pypi.org/project/selenium/#history
After release of selenium 4.17.0 our builds started failing due to the conflict between versions of selenium and typing extensions. Starting from 4.17.0 selenium requires typing-extensions in version 4.9.0.
Using selenium 4.17.0 with older typing-extensions (matched by PIP) ends with build errors. Enforcing selenium==4.16.0 fixes the issue.
Selenium wheel package should define strong requirement on typing-extensions version in metadata.
How can we reproduce the issue?
Relevant log output
Operating System
Linux
Selenium version
Python 4.17.0
What are the browser(s) and version(s) where you see this issue?
Firefox
What are the browser driver(s) and version(s) where you see this issue?
Any
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: