Installs ChromeDriver executable with pip or setup.py.
Usage
Manual Installation
Clone the repository:
(e)$ git clone https://github.com/peterhudec/chromedriver_installer.gitInstall the most recent ChromeDriver version without verifying checksum.
(e)$ python setup.py installInstall specific ChromeDriver version without verifying checksum.
(e)$ python setup.py install --chromedriver-version=2.10Install specific ChromeDriver version and verify checksum. Note that you can pass multiple coma-separated checksums to the --chromedriver-checksums option. This is useful if you plan to install ChromeDriver on various platforms because there is separate version with different checksum for each platform. You can get the checksums for specific version/platform combinations at the chromedriver download URL.
(e)$ python setup.py install \
--chromedriver-version=2.10 \
--chromedriver-checksums=4fecc99b066cb1a346035bf022607104,058cd8b7b4b9688507701b5e648fd821After install, there should be the chromedriver executable available in your path:
(e)$ which chromedriver
/home/andypipkin/e/bin/chromedriver
(e)$ chromedriver --version
ChromeDriver 2.10.267518
(e)$ chromedriver
Starting ChromeDriver (v2.10.267518) on port 9515
Only local connections are allowed.Installation With PIP
The same as before except you need to pass the install options wrapped in pip’s --install-option="" option.
(e)$ pip install chromedriver_installer \
--install-option="--chromedriver-version=2.10" \
--install-option="--chromedriver-checksums=4fecc99b066cb1a346035bf022607104,058cd8b7b4b9688507701b5e648fd821"Installation With easy_install
I can’t seem to find a way to make easy_install pass user options to setup.py so you only can install the most recent ChromeDriver version with easy_install.
How it Works
The build_scripts command of the setup.py script invoked by python setup.py install downloads, the ChromeDriver zip archive version specified in the --chromedriver-version option from http://chromedriver.storage.googleapis.com/index.html to the temp directory of the operating system. If the --chromedriver-checksums option is set, the archive is validated against the supplied checksums (you can get the checksums at the aforementioned URL). If the validation failed, the installation exits with an error. If the validation was successful or if the --chromedriver-checksums option is not set, the archive will be unzipped to the build directory and installed as an executable to the bin directory.
If the --chromedriver-version option is ommited, it installs the most recent chromedriver version without checksum validation.
Testing
You need tox to run the tests.
(e)$ git clone https://github.com/peterhudec/chromedriver_installer.git
(e)$ pip install -r requirements.txt
(e)$ tox1 maintainer
Release files for chromedriver-installer-nwmqpa 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| chromedriver_installer_nwmqpa-0.0.9.tar.gz | 4.3 kB | Details |
Release files / chromedriver_installer_nwmqpa-0.0.9.tar.gz
| Download URL | chromedriver_installer_nwmqpa-0.0.9.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f51509a3332c3094d2c9a228e822e5fbb6c7d697fe753cbfa30288be446b81c7
|
|
BLAKE2b-256 checksum How to use checksums |
989c740d0d0463924a3e3b8ed8d47d6406da0a25e76d204aff92b011c40b1e39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.9
|
