Splinter doesn't work with Selenium 4.0
See original GitHub issueSelenium 4.0.0 was just released. With the latest version there are apparently some API changes that Splinter doesn’t handle well.
Our issue was TypeError: __init__() got an unexpected keyword argument 'timeout'
on https://github.com/cobrateam/splinter/blob/253a6f21699a60651943bac11cf87a24da4d5a81/splinter/driver/webdriver/firefox.py#L71
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10 (4 by maintainers)
Top Results From Across the Web
splinter Documentation
This version does not work with firefox 17. Improvements. • remove deprecated driver names. • update lxml version. • update selenium version to ......
Read more >Xpath Not Selecting Correct Element Using Splinter/Selenium ...
I'm trying to make a scraper to scrape Google Map Pack data. I'm using Splinter to do so. I've managed to select the...
Read more >Releases · cobrateam/splinter - GitHub
Removed required selenium import for error handling, making it possible to use splinter without installing selenium (as long as a selenium driver isn't...
Read more >pytest-splinter4 - PyPI
A pytest plugin for splinter. pytest-splinter4 is a fork of pytest-splinter with added features and fixes to support newer versions of pytest, pytest-xdist, ......
Read more >Build timeout on Travis CI when testing with lettuce + splinter ...
I tried splitting my tests in separate features files, same problem. It's doesn't seem to be caused ... Turns out it was hanging...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@blaise-io 0.16.0’s release pins selenium 3 in order to prevent dependency conflicts, it has nothing to do with getting selenium 4 to work.
Selenium 4 compatibility is coming soon-ish.
Fixed by #963