Looks like we cannot locate the path the 'chromedriver' if limit is included
See original GitHub issueOS: osx 10.12.6
Python version: 3.6.5
Issue steps:
When running CLI with -l or --limit option specified, the following error is returned.
Looks like we cannot locate the path the 'chromedriver' (use the '--chromedriver' argument to specify the path to the executable.) or google chrome browser is not installed on your machine
executing without -l works fine.
Attempted to use json input but still returning same error. json file contents below:
{ "Records": [ {"keywords": "tops","limit": 1000}, {"keywords": "jacket","limit": 1000} ] }
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:31 (8 by maintainers)
Top Results From Across the Web
Using Chromedriver with Google Images download
1 Answer 1 · If that doesn't work, then hardcode line 177 of google_images_download.py where it says browser = webdriver. · MyNameIsCaleb's ...
Read more >ChromeDriver - WebDriver for Chrome - Getting started
Any of these steps should do the trick: include the ChromeDriver location in your PATH environment variable. (Java only) specify its location via...
Read more >Tips for building large image datasets - Fast.ai forums
Looks like we cannot locate the path the 'chromedriver' (use the '–chromedriver' argument to specify the path to the executable.) ...
Read more >Chromedriver via Selenium? : Forums - PythonAnywhere
I get this error - I know the element is present on the page I'm visiting and have tested dozens of times via...
Read more >Error selenium common exceptions WebDriverException ...
You can test if it actually is in the PATH, if you open a cmd and type in chromedriver (assuming your chromedriver executable...
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
OK, I was able to make it work like this:
I had this issue too, the issue is that all command line arguments are ignored when the config file argument is present.
googleimagesdownload -cf cfg.json --chromedriver '/usr/bin/chromedriver'
will ignore the--chromedriver
argument. You can add it to the configuration file{ "Records": [ {"keywords": "tops","limit": 1000, "chromedriver": "/usr/bin/chromedriver"}, {"keywords": "jacket","limit": 1000, "chromedriver": "/usr/bin/chromedriver"} ] }
, a bit too verbose, but it works.