Ethereum Utilities
Common utility functions for python code that interacts with Ethereum
Read the documentation.
View the change log.
Installation
python -m pip install eth-utils
Developer Setup
If you would like to hack on eth-utils, please check out the Snake Charmers Tactical Manual for information on how we do:
- Testing
- Pull Requests
- Documentation
We use pre-commit to maintain consistent code style. Once
installed, it will run automatically with every commit. You can also run it manually
with make lint. If you need to make a commit that skips the pre-commit checks, you
can do so with git commit --no-verify.
Development Environment Setup
You can set up your dev environment with:
git clone git@github.com:ethereum/eth-utils.git
cd eth-utils
virtualenv -p python3 venv
. venv/bin/activate
python -m pip install -e ".[dev]"
pre-commit install
Update Networks
The list of networks resides in the JSON file under eth_utils/__json/eth_networks.json. This file is used to initialize Networks, which can be used to obtain network information with a chain ID.
Run the script to update the JSON file with the response from the remote list.
python update_networks.py
If there are new networks they will appear in the JSON file. After checking the updates, open a PR to make them available in a new release.
Release setup
To release a new version:
make release bump=$$VERSION_PART_TO_BUMP$$
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. This is typically done from the
main branch, except when releasing a beta (in which case the beta is released from main,
and the previous stable branch is released from said branch).
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"
Release files for eth-utils 6.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eth_utils-6.0.0.tar.gz | 123.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eth_utils-6.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 225.9 kB
Release files / eth_utils-6.0.0.tar.gz
| Download URL | eth_utils-6.0.0.tar.gz |
|---|---|
| Size | 123.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb54b2f82dd300d3142c49a89da195e823f5e5284d43203593f87c67bad92a96
|
|
BLAKE2b-256 checksum How to use checksums |
e91b0b8548da7b31eba87ed58bca1d0de5dcb13a6c113e02c09019ec5a6716ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / eth_utils-6.0.0-py3-none-any.whl
| Download URL | eth_utils-6.0.0-py3-none-any.whl |
|---|---|
| Size | 102.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63cf48ee32c45541cb5748751909a8345c470432fb6f0fed4bd7c53fd6400469
|
|
BLAKE2b-256 checksum How to use checksums |
5345a20b907227b9d1aea2e36f7b12818d055629ca9bc65fc282b45738f28ca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
