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

`bash pip install py-geth `

Or to install with gevent support

`bash pip install py-geth[gevent] `

> Set the environment variable GETH_ASYNC_GEVENT to use gevent based threading.

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.6.0.tar.gz (16.0 kB view details)

Uploaded Source

Built Distributions

py_geth-1.6.0-py3-none-any.whl (20.3 kB view details)

Uploaded Python 3

py-geth-1.6.0.macosx-10.10-x86_64.tar.gz (12.8 kB view details)

Uploaded Source

File details

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

File metadata

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

File hashes

Hashes for py-geth-1.6.0.tar.gz
Algorithm Hash digest
SHA256 ddbb41473ebde041c29187619d1d671753ad32c7e8c272342d85ada5e82639e4
MD5 943b36f25b1dfca1fe6eccb58c3f257f
BLAKE2b-256 34de6676eee3598bcb4bccf51b328c9cb86edb622a4f13dcdf27b92adafa16e4

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for py_geth-1.6.0-py3-none-any.whl
Algorithm Hash digest
SHA256 78ac21219b61382f8760342d0b8beec76924826a110af332a5938cf23b9cd2e3
MD5 72b5fd80e41dcd13f09238c9171bae6c
BLAKE2b-256 d59a4f8fb5156caccfc10b51db9b30877d0ebd1f6688fe1beab2a5f18921492e

See more details on using hashes here.

File details

Details for the file py-geth-1.6.0.macosx-10.10-x86_64.tar.gz.

File metadata

File hashes

Hashes for py-geth-1.6.0.macosx-10.10-x86_64.tar.gz
Algorithm Hash digest
SHA256 9719583ff8fa77a9e1984ab71c2029f8650d90f8159f2f3899a7cc0bd3355796
MD5 61f79da25d5fe646c6bb234dbda4d329
BLAKE2b-256 71d2690209d3c3024432a5701b5ed125842e4b15d9172fcab82b688332ec2506

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