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

Uploaded Source

Built Distributions

py_geth-1.5.0-py3-none-any.whl (17.9 kB view details)

Uploaded Python 3

py-geth-1.5.0.macosx-10.12-x86_64.tar.gz (11.6 kB view details)

Uploaded Source

File details

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

File metadata

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

File hashes

Hashes for py-geth-1.5.0.tar.gz
Algorithm Hash digest
SHA256 d26fa33a76f4ecde8a1e381c437af4f8cc0cdcad5fb85e842751c8cbd564c6b9
MD5 eb393eb1adf9a6b35ac130e184e293d9
BLAKE2b-256 193ee6f27d0306cc036948e7a22777bd42248543d2bb54418a2e8c01366e65bc

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for py_geth-1.5.0-py3-none-any.whl
Algorithm Hash digest
SHA256 ed1bc4bb7c99e2f72151c511962a99c1982ca1886125a95184040515916ce714
MD5 049dc87b9dda701603ebba544122cf4f
BLAKE2b-256 59f3ca8a3ba4264fa1eaf90e366679fab84a0df1beb2023c6e53e36f2997d5de

See more details on using hashes here.

File details

Details for the file py-geth-1.5.0.macosx-10.12-x86_64.tar.gz.

File metadata

File hashes

Hashes for py-geth-1.5.0.macosx-10.12-x86_64.tar.gz
Algorithm Hash digest
SHA256 c4821d120328165fd517c39755449da10201194f22f86664328d5ec9780c2836
MD5 2e269f4c5be2531338fed3fb8dbf65aa
BLAKE2b-256 36773024460d0ef256e2c6a0c0d319d85096b3647b6527c4c6abafb62415c284

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