Skip to content

chromedriver not running (python 2.5 32bit, windows) #173

Closed
mariodev opened this Issue Oct 2, 2012 · 8 comments

3 participants

@mariodev
mariodev commented Oct 2, 2012

Inside file "splinter\driver\webdriver\chrome.py"

calling "self._patch_subprocess()" somehow breaks running of the proccess itself, throwing "not in path" exception msg.

It runs chrome only when I comment it out.

@bernardofire
Cobra Team member

do we support python 2.5? (I'm not saying that's the issue)

@mariodev
mariodev commented Oct 3, 2012

2.7 has the same issues.

Yeah, the installation page saying support for 2.5 - 2.7, which I think should be changed, since selenium==2.25.0 does not support py2.5 (although it works after adding some compatibility to the selenium source code)

@andrewsmedina
Cobra Team member

splinter support python 2.5, but officially does not support windows.

I believe that it should work on windows and if you downloading the chrome driver and put him in the path should solve your problem.

@mariodev
mariodev commented Oct 9, 2012

@andrewsmedina I did put it in path, but it's not the issue. It gives the "path error" incorrectly, since the problem is with _patch_subprocess() method

@andrewsmedina
Cobra Team member

@mariodev how I said before, splinter does not support windows officially.

Internally, splinter has a method to mute the webdriver log. This method does not works on windows. I will remove it.

@andrewsmedina andrewsmedina added a commit that referenced this issue Oct 11, 2012
@andrewsmedina andrewsmedina Removed methods to mute the webdriver log.
Related to #173.

Internally, splinter has a method to mute the webdriver log. This method
does not works on windows. I will remove it.
55999c8
@andrewsmedina
Cobra Team member

Done. @mariodev can you test please?

@mariodev

It works now. Thank you for the fix :)

@andrewsmedina
Cobra Team member

I will make a release with it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.