[🐛 Bug]: Chrome not launching after Python update 3.10.0->3.12.4

[Harrier-Du-Bois]

What happened?

I have a working test setup which is running as expected in a venv using python 3.10.0 under Windows 11.
I considered updating to python 3.12.4, so I created a new venv using 3.12.4 and installing the same decencies as I have in my original venv through a requirements.txt.

Problem is when using 3.12.4 the code execution hangs at "driver = webdriver.Chrome ()". I.e. it doesn't pause or stop or break out, it just continues running with no visible progress. There is no output or error messages.

So I created another new test venv, using python 3.10 again, installed same requirements.txt and this new venv works again.

So from my pov I have two identical (apart from their name) new venvs, one using py 3.10.0, the other py 3.12.4, the former running my existing tests, the latter just stopping when initiating the chrome webdriver.

Is there a know issue when upgrading from py 3.10.0?

Selenium ver: 4.26.1
It does download the latest chromedriver, 129.0.6668.100
I am unable to change the Chrome browser version, which is 129.0.6668.90

How can we reproduce the issue?

See above

Relevant log output

No output in terminal

Operating System

Win11

Selenium version

Python 4.26.1

What are the browser(s) and version(s) where you see this issue?

Chrome 129.0.6668.90

What are the browser driver(s) and version(s) where you see this issue?

chromedriver 129.0.6668.100

Are you using Selenium Grid?

no

[github-actions]

@Harrier-Du-Bois, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

You need to upgrade to the latest Selenium version.

[Harrier-Du-Bois]

I did via pip, is there a newer version than 4.26.1?

[diemol]

I misread something on the issue, reopening.

[VietND96]

We setup the CI to run few example tests with range of python version 3.8 to 3.13. However didn't see that behavior at version 3.12 - https://github.com/SeleniumHQ/seleniumhq.github.io/actions/runs/11893970956/job/33140147336

[Harrier-Du-Bois]

We setup the CI to run few example tests with range of python version 3.8 to 3.13. However didn't see that behavior at version 3.12 - https://github.com/SeleniumHQ/seleniumhq.github.io/actions/runs/11893970956/job/33140147336

Thanks for checking, even tho I'm still in my same spot now... I don't really see what could be causing this behaviour on my end.
Do you think it could be the specific python minor version 3.12.4? If I'm not mistaken you're using 3.12.7 in your test, could it be that particular one that's causing this? Sadly I can't just install new versions as all of that is handled by my organisation, but I'll try and recreate my setup at home and see if results differ with py 3.12.7 or a newer version.

[VietND96]

For example multiple versions in your machine, and python3.12 is the command point to 3.12. Try to execute this command once

python3.12 -m ensurepip --upgrade
python3.12 -m pip install --upgrade setuptools

Then, create a new test venv to see any help.