Skip to main content

Web3.py

Project description

Web3.py

Join the chat at https://gitter.im/ethereum/web3.py

Build Status

A Python implementation of web3.js

  • Python 3.6+ support

Read more in the documentation on ReadTheDocs. View the change log on Github.

Developer Setup

git clone git@github.com:ethereum/web3.py.git
cd web3.py

Please see OS-specific instructions for:

Then run these install commands:

virtualenv venv
. venv/bin/activate
pip install -e .[dev]

For different environments, you can set up multiple virtualenv. For example, if you want to create a venvdocs, then you do the following:

virtualenv venvdocs
. venvdocs/bin/activate
pip install -e .[docs]
pip install -e .

Using Docker

If you would like to develop and test inside a Docker environment, use the sandbox container provided in the docker-compose.yml file.

To start up the test environment, run:

docker-compose up -d

This will build a Docker container set up with an environment to run the Python test code.

Note: This container does not have go-ethereum installed, so you cannot run the go-ethereum test suite.

To run the Python tests from your local machine:

docker-compose exec sandbox bash -c 'pytest -n 4 -f -k "not goethereum"'

You can run arbitrary commands inside the Docker container by using the bash -c prefix.

docker-compose exec sandbox bash -c ''

Or, if you would like to just open a session to the container, run:

docker-compose exec sandbox bash

Testing Setup

During development, you might like to have tests run on every file save.

Show flake8 errors on file change:

# Test flake8
when-changed -v -s -r -1 web3/ tests/ ens/ -c "clear; flake8 web3 tests ens && echo 'flake8 success' || echo 'error'"

You can use pytest-watch, running one for every Python environment:

pip install pytest-watch

cd venv
ptw --onfail "notify-send -t 5000 'Test failure ⚠⚠⚠⚠⚠' 'python 3 test on web3.py failed'" ../tests ../web3

Or, you can run multi-process tests in one command, but without color:

# in the project root:
pytest --numprocesses=4 --looponfail --maxfail=1
# the same thing, succinctly:
pytest -n 4 -f --maxfail=1

How to Execute the Tests?

  1. Setup your development environment.

  2. Execute tox for the tests

There are multiple components of the tests. You can run test to against specific component. For example:

# Run Tests for the Core component (for Python 3.6):
tox -e py36-core

# Run Tests for the Core component (for Python 3.7):
tox -e py37-core

If for some reason it is not working, add --recreate params.

tox is good for testing against the full set of build targets. But if you want to run the tests individually, pytest is better for development workflow. For example, to run only the tests in one file:

pytest tests/core/gas-strategies/test_time_based_gas_price_strategy.py

Release setup

For Debian-like systems:

apt install pandoc

The final step before releasing is to build and test the code that will be released. There is a test script that will build and install the wheel locally, then generate a temporary virtualenv where you can do some smoke testing:

# Branch name could be either master or a version branch - ex. v5

$ git checkout <branch name> && git pull

$ make package

# in another shell, navigate to the virtualenv mentioned in output of ^

# load the virtualenv with the packaged trinity release
$ source package-smoke-test/bin/activate

# smoke test the release
$ pip install ipython
$ ipython
>>> from web3.auto import w3
>>> w3.isConnected()
>>> ...

# Preview the upcoming release notes
$ towncrier --draft

To release a new version:

make release bump=$$VERSION_PART_TO_BUMP$$

To preview the upcoming release notes:

towncrier --draft

How to bumpversion

The version format for this repo is {major}.{minor}.{patch} for stable, and {major}.{minor}.{patch}-{stage}.{devnum} for unstable (stage can be alpha or beta).

To issue the next version in line, specify which part to bump, like make release bump=minor or make release bump=devnum.

If you are in a beta version, make release bump=stage will switch to a stable.

To issue an unstable version when the current version is stable, specify the new version explicitly, like make release bump="--new-version 4.0.0-alpha.1 devnum"

Project details


Release history Release notifications | RSS feed

Download files

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

Source Distribution

web3-5.12.0b1.tar.gz (343.5 kB view details)

Uploaded Source

Built Distribution

web3-5.12.0b1-py3-none-any.whl (412.4 kB view details)

Uploaded Python 3

File details

Details for the file web3-5.12.0b1.tar.gz.

File metadata

  • Download URL: web3-5.12.0b1.tar.gz
  • Upload date:
  • Size: 343.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.6

File hashes

Hashes for web3-5.12.0b1.tar.gz
Algorithm Hash digest
SHA256 39b9d5c63b0afdf838d2ead3d2a740e66183d0bf703e17deeb2bd0d9a93e01ff
MD5 4c06748cd6fcdb52e15b4f770d61b3d5
BLAKE2b-256 81624e607f6d3beae4f8c261518d78b8c6f46cb34138494e7037046010ba562a

See more details on using hashes here.

File details

Details for the file web3-5.12.0b1-py3-none-any.whl.

File metadata

  • Download URL: web3-5.12.0b1-py3-none-any.whl
  • Upload date:
  • Size: 412.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.6

File hashes

Hashes for web3-5.12.0b1-py3-none-any.whl
Algorithm Hash digest
SHA256 0fa5e433a62cd00270751692302f79c5a5397703763836757e8b7fa680a1d7e3
MD5 f69dbb85dc17bf606cca24dd82151d29
BLAKE2b-256 105ab33f63f3b9bf6c6e5479595896940efc890316d7b5ad2f39b6c9a23c4a2b

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