-
Notifications
You must be signed in to change notification settings - Fork 76
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
macOS - Error with chromedriver? #18
Comments
|
Thanks for the fast response.
But with |
In
for the
What can I do for testing and trying, too? |
How did you install chromedriver? If you installed it via homebrew it creates only a hardlink to chromedriver in e. g. '/usr/local/bin/chromedriver'. You have to follow that hardlink (or alias in MacOS) to get the correct path to your chromedriver binary. For example, I have changed my chromedriver path to maybe try |
Okay, thanks for your help. I thought I know about those variables but I didn't get it running.
after typing
With these informations. Do you have another hint for me? Should I enter I think I didn't understand the |
I tried to install it again by just the zip-file. Put it in the
and nothing happens. In the
Maybe the someone knows what could be wrong because of the |
Your path leads to a homebrew formula (a ruby script containing a set of commands to install a certain software), not the chromedriver binary, which has no extension, just sth. like my example in the post above
it should be something similar as in my config, thus a
As I already said in a post above, locate your chromedriver binary with the terminal command
That was the way I installed it, sorry for the irritiation. I hope you will be able to get it to run finally. Have phun! |
hello, I have installed the chrome driver with homebrew. I still get this error
I have also updated my PATH :
what can i do at this point? |
After starting with
python chat.py Wonderfulname
nothing happens than this message:Does anyone have a hint for me?
Thank you. I have the newest Chrome version, the newest Chromedriver, ...!?
The text was updated successfully, but these errors were encountered: