Skip to content
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

3.5.2 - Minor changes and fixes #1452

Merged
merged 1 commit into from
Aug 9, 2023
Merged

3.5.2 - Minor changes and fixes #1452

merged 1 commit into from
Aug 9, 2023

Conversation

ultrafunkamsterdam
Copy link
Owner

  • removed search paths for Chrome Canary and Chrome Beta from find_chrome_executable() since chromedriver is always behind schedule so that means a driver for newer versions than current main could not be found and raises Exception.

  • Changed/Fixed wrong binary version caused by patcher. Due to multi-threading people and a mistake fromy my side, the driver binary currently on disk was always used instead of getting new ones. even if you did not use multithreading. so even outdated binaries where kept, hence many people got the dreaded "wrong version" error.

    • so for multithreading people, it now only keeps the most recent binary and throws away others.
    • for normal people, you will get a fresh binary, like you deserve ;)
  • Added more descriptive exceptions when Chrome binary could not be found origin no connection could be made to Chrome.

  • some stuff i forgot, like bumping version on pypa so it installs correct version :)

* removed search paths for Chrome Canary and Chrome Beta from find_chrome_executable()
    since chromedriver is always behind schedule so that means a driver for newer versions than current main could not be found and raises Exception.

* Changed/Fixed wrong binary version caused by patcher.
  Due to multi-threading people and a mistake fromy my side,
  the driver binary currently on disk was always used instead of getting new ones. even if you did not use multithreading.
  so even outdated binaries where kept!
  for multithreading people, it now only keeps the most recent binary and throws away others.
  for normal people, you will get the binary you deserve ;)

* Added more descriptive exceptions when Chrome binary could not be found origin
  no connection could be made to Chrome.

* some stuff i forgot
@ultrafunkamsterdam ultrafunkamsterdam merged commit a415e40 into master Aug 9, 2023
4 checks passed
@rafamelo01
Copy link

Even if i specify the driver_executable_path (a downloaded chromedriver) if it's an older version now it throws away and download a new one? Or now i dont need more download it before, just let the UC download itself. Im using multithreaded

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants