Web3.py
A Python implementation of NewChain Web3 which is forked from https://github.com/ethereum/web3.py.
- Python 3.7.2+ support
Developer Setup
git clone git@github.com:xiawu/newchain-web3.py.git
cd newchain-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 ../newchain_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?
-
Execute
toxfor 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.5):
tox -e py35-core
# Run Tests for the Core component (for Python 3.6):
tox -e py36-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, py.test is better for development workflow. For example, to run only the tests in one file:
py.test tests/core/gas-strategies/test_time_based_gas_price_strategy.py
Release setup
For Debian-like systems:
apt install pandoc
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.
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"
Metadata
Release files for newchain-web3 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| newchain-web3-0.2.2.tar.gz | 434.5 kB | Without provenance | Details for newchain-web3-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| newchain_web3-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for newchain_web3-0.2.2-py3-none-any.whl |
Total release size: 977.7 kB
Release files / newchain-web3-0.2.2.tar.gz
| Download URL | newchain-web3-0.2.2.tar.gz |
|---|---|
| Size | 434.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b5a7e022e74cbc06fed092daff3d91eec01fbf0e247c916924f80a2460b809f
|
|
BLAKE2b-256 checksum How to use checksums |
11c5e8ec23d39e9ba41f86eec211cf6e38c08bdff0ce17026fe5b089545c4af0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.28.1 setuptools/65.3.0 requests-toolbelt/0.9.1 tqdm/4.64.1 CPython/3.8.14
|
Release files / newchain_web3-0.2.2-py3-none-any.whl
| Download URL | newchain_web3-0.2.2-py3-none-any.whl |
|---|---|
| Size | 543.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9785c232be6d009fbe4944065761d217f5a24ca359154afd9bfbc74b56a7ee08
|
|
BLAKE2b-256 checksum How to use checksums |
5c1d08670c05003ad702cf19100b38f6dc137117ed16547f4d0c3cdd9212fc67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.8.3 requests/2.28.1 setuptools/65.3.0 requests-toolbelt/0.9.1 tqdm/4.64.1 CPython/3.8.14
|
Security for newchain-web3 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.