Run Go-Ethereum as a subprocess
[![Build Status](https://travis-ci.org/pipermerriam/py-geth.png)](https://travis-ci.org/pipermerriam/py-geth) [![Documentation Status](https://readthedocs.org/projects/py-geth/badge/?version=latest)](https://readthedocs.org/projects/py-geth/?badge=latest) [![PyPi version](https://pypip.in/v/py-geth/badge.png)](https://pypi.python.org/pypi/py-geth) [![PyPi downloads](https://pypip.in/d/py-geth/badge.png)](https://pypi.python.org/pypi/py-geth)
Python wrapper around running geth as a subprocess
This library requires the geth executable to be present.
`bash pip install py-geth `
Or to install with gevent support
`bash pip install py-geth[gevent] `
And then enable gevent based threads by setting the environment variable GETH_THREADING_BACKEND=gevent.
To run geth connected to the mainnet
`python >>> from geth import LiveGethProcess >>> geth = LiveGethProcess() >>> geth.start() `
Or a private local chain for testing. These require you to give them a name.
`python >>> from geth import DevGethProcess >>> geth = DevGethProcess('testing') >>> geth.start() `
By default the DevGethProcess sets up test chains in the default datadir used by geth. If you would like to change the location for these test chains, you can specify an alternative base_dir.
`python >>> geth = DevGethProcess('testing', '/tmp/some-other-base-dir/') >>> geth.start() `
Each instance has a few convenient properties.
`python >>> geth.data_dir "~/.ethereum" >>> geth.rpc_port 8545 >>> geth.ipc_path "~/.ethereum/geth.ipc" >>> geth.accounts ['0xd3cda913deb6f67967b99d67acdfa1712c293601'] >>> geth.is_alive False >>> geth.is_running False >>> geth.is_stopped False >>> geth.start() >>> geth.is_alive True # indicates that the subprocess hasn't exited >>> geth.is_running True # indicates that `start()` has been called (but `stop()` hasn't) >>> geth.is_stopped False >>> geth.stop() >>> geth.is_alive False >>> geth.is_running False >>> geth.is_stopped True `
When testing it can be nice to see the logging output produced by the geth process. py-geth provides a mixin class that can be used to log the stdout and stderr output to a logfile.
`python >>> from geth import LoggingMixin, DevGethProcess >>> class MyGeth(LoggingMixin, DevGethProcess): ... pass >>> geth = MyGeth() >>> geth.start() `
All logs will be written to logfiles in ./logs/ in the current directory.
The underlying geth process can take additional time to open the RPC or IPC connections, as well as to start mining if it needs to generate the DAG. You can use the following interfaces to query whether these are ready.
`python >>> geth.is_rpc_ready True >>> geth.wait_for_rpc(timeout=30) # wait up to 30 seconds for the RPC connection to open >>> geth.is_ipc_ready True >>> geth.wait_for_ipc(timeout=30) # wait up to 30 seconds for the IPC socket to open >>> geth.is_dag_ready True >>> geth.is_mining True >>> geth.wait_for_dag(timeout=600) # wait up to 10 minutes for the DAG to generate. `
> The DAG functionality currently only applies to the DAG for epoch 0.
# Aboutn DevGethProcess
The DevGethProcess is designed to facilitate testing. In that regard, it is preconfigured as follows.
If you are running with mining enabled (which is default for DevGethProcess then you will likely need to generate the DAG manually. If you do not, then it will auto-generate the first time you run the process and this takes a while.
To generate it manually:
`sh $ geth makedag 0 ~/.ethash `
This is especially important in CI environments like Travis-CI where your process will likely timeout during generation.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|File Name & Checksum SHA256 Checksum Help||Version||File Type||Upload Date|
|py-geth-1.8.0.macosx-10.12-x86_64.tar.gz (13.2 kB) Copy SHA256 Checksum SHA256||any||Dumb Binary||Apr 27, 2017|
|py_geth-1.8.0-py3-none-any.whl (20.7 kB) Copy SHA256 Checksum SHA256||3.5||Wheel||Apr 27, 2017|
|py-geth-1.8.0.tar.gz (14.5 kB) Copy SHA256 Checksum SHA256||–||Source||Apr 27, 2017|