Skip to main content

Run Go-Ethereum as a subprocess

Project description

# PyGeth

[![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-hypernode.com/pypi/py-geth) [![PyPi downloads](https://pypip.in/d/py-geth/badge.png)](https://pypi-hypernode.com/pypi/py-geth)

Python wrapper around running geth as a subprocess

# Dependency

This library requires the geth executable to be present.

# Quickstart

Installation

`sh pip install py-geth `

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.

  • A single account is created and allocated 1 billion ether.

  • All APIs are enabled on both rpc and ipc interfaces.

  • Account 0 is unlocked

  • Networking is configured to not look for or connect to any peers.

  • The networkid of 1234 is used.

  • Verbosity is set to 5 (DEBUG)

  • Mining is enabled with a single thread.

  • The RPC interface tries to bind to 8545 but will find an open port if this port is not available.

  • The DevP2P interface tries to bind to 30303 but will find an open port if this port is not available.

# Gotchas

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

py-geth-1.4.0.tar.gz (12.8 kB view details)

Uploaded Source

Built Distributions

py_geth-1.4.0-py3-none-any.whl (17.8 kB view details)

Uploaded Python 3

py-geth-1.4.0.macosx-10.11-x86_64.tar.gz (11.5 kB view details)

Uploaded Source

File details

Details for the file py-geth-1.4.0.tar.gz.

File metadata

  • Download URL: py-geth-1.4.0.tar.gz
  • Upload date:
  • Size: 12.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No

File hashes

Hashes for py-geth-1.4.0.tar.gz
Algorithm Hash digest
SHA256 ab3256f581caa353d24e8a8fe1c24aeb737ef270b792d154953831959744f837
MD5 83649205a843c04c3be3ec38c7d96530
BLAKE2b-256 7b8c1edb0fbed67ce5308c0e3a1c711d196f0fc03b38ef2be4342dfb5b10daf8

See more details on using hashes here.

File details

Details for the file py_geth-1.4.0-py3-none-any.whl.

File metadata

File hashes

Hashes for py_geth-1.4.0-py3-none-any.whl
Algorithm Hash digest
SHA256 de74cd8cf797073295e4404df58e705b9163c1b62174c8207d2b9f48967a5771
MD5 de8a8b540993d224a0557f52450d27bc
BLAKE2b-256 5b433639a65e070aad212d2806b98903dc3f3979d4e729c07bebf2fccf2ebdf5

See more details on using hashes here.

File details

Details for the file py-geth-1.4.0.macosx-10.11-x86_64.tar.gz.

File metadata

File hashes

Hashes for py-geth-1.4.0.macosx-10.11-x86_64.tar.gz
Algorithm Hash digest
SHA256 b732e6ad2b9216dd2bf8a8c0a3054b512c405499a4e5c1491a143e0b5d3f8a30
MD5 f9491ecb22243a525a766019fef0b118
BLAKE2b-256 4b9b816cde53c63e92c87fb113297e9a2c9ca21209b85241c092d4bf1d34ef92

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page