Web3.py
A Python implementation of web3.js
- Python 3.6+ support
Developer Setup
[](https://gitter.im/vnscoin/web3.py?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](https://circleci.com/gh/vnscoin/web3.py)
A Python implementation of [web3.js](https://github.com/vnscoin/web3.js)
* Python 3.6+ support
## Developer Setup
```sh
git clone git@github.com:vnscoin/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 .
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.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
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"
git clone git@github.com:vnscoin/web3.py.git cd web3.py
Please see OS-specific instructions for:
- [Linux](docs/README-linux.md#Developer-Setup)
- [Mac](docs/README-osx.md#Developer-Setup)
- [Windows](docs/README-windows.md#Developer-Setup)
Then run these install commands:
```sh
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 .
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.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
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"
Metadata
Release files for vns-web3 0.0.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 |
|---|---|---|---|---|
| vns_web3-0.0.2.tar.gz | 182.3 kB | Without provenance | Details for vns_web3-0.0.2.tar.gz |
Release files / vns_web3-0.0.2.tar.gz
| Download URL | vns_web3-0.0.2.tar.gz |
|---|---|
| Size | 182.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
350a9fdcf6ba2200e765eb9f50fe78696856a414bec1a5a78d90251ae10e9843
|
|
BLAKE2b-256 checksum How to use checksums |
3497663a8f059ba2abb58d1ac079c4b16cb83fb2d2b1399484ac8567fc91ba91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.3
|
Security for vns-web3 0.0.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.