This release is a pre-release and may not be stable for production use.
dopple
HTTP proxy to Unix Socket based JSON-RPC servers
Installation
pip install dopple
Use
dopple ~/.ethereum/geth.ipc http://127.0.0.1:8545
These values above are the default ones too. If they match your current configuration, they can be ommitted.
Check out --help option for more information.
Read more in the documentation on ReadTheDocs. View the change log.
Developer Setup
If you would like to hack on dopple, please check out the Snake Charmers Tactical Manual for information on how we do:
- Testing
- Pull Requests
- Code Style
- Documentation
Development Environment Setup
You can set up your dev environment with:
git clone git@github.com:ethereum/dopple.git
cd dopple
virtualenv -p python3 venv
. venv/bin/activate
pip install -e .[dev]
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 dopple/ tests/ -c "clear; flake8 dopple tests && echo 'flake8 success' || echo 'error'"
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
Run in one thread, with color and desktop notifications:
cd venv
ptw --onfail "notify-send -t 5000 'Test failure ⚠⚠⚠⚠⚠' 'python 3 test on dopple failed'" ../tests ../dopple
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. This is typically done from the
master branch, except when releasing a beta (in which case the beta is released from master,
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"
Metadata
Release files for dopple 0.4.0a0
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 |
|---|---|---|---|---|
| dopple-0.4.0a0.tar.gz | 6.3 kB | Without provenance | Details for dopple-0.4.0a0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dopple-0.4.0a0-py3-none-any.whl | Python 3 | none | any | Details for dopple-0.4.0a0-py3-none-any.whl |
Total release size: 16.2 kB
Release files / dopple-0.4.0a0.tar.gz
| Download URL | dopple-0.4.0a0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32fe2c9fa1254f16f936893be8f8139b64a5629c2fe0c49bfe9ba41d3894387a
|
|
BLAKE2b-256 checksum How to use checksums |
95b9d79e7a9675ac0d775082baf7a2be8eda2740151421aec84fc6d39b40e2c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.3
|
Release files / dopple-0.4.0a0-py3-none-any.whl
| Download URL | dopple-0.4.0a0-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8a9e307e691036423c80a7199fb03f4eb7167e11714ec809bf617c59add30ee
|
|
BLAKE2b-256 checksum How to use checksums |
fa68b16171e4f8f4e8bbe6a6cc2cc24cc47688ac82459af8505ffd717bca9205
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.3
|
Security for dopple 0.4.0a0
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.