The Python implementation of the libp2p networking stack 🐍 [under development]
Go to file
2019-11-25 21:44:29 +01:00
.circleci Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00
.github Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00
.project-template Make template filler more BSD friendly 2018-06-06 18:49:12 -06:00
docs Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00
newsfragments Add internal type for release notes 2019-11-25 21:44:29 +01:00
tests/core silence flake8 error during module import test 2018-02-06 16:10:25 -08:00
.bumpversion.cfg init 2018-01-24 16:00:28 -08:00
.gitignore Add vim .swo files and .mypy_cache to .gitignore 2019-06-03 12:22:46 -07:00
.pydocstyle.ini Add docstring checking with pydocstyle 2019-01-24 13:57:17 -07:00
LICENSE Remove attribution to specific person 2019-03-25 15:14:04 -06:00
Makefile Separate release-note build from release 2019-11-25 21:44:29 +01:00
mypy.ini Add mypy support 2019-04-26 18:22:24 +02:00
pyproject.toml Add internal type for release notes 2019-11-25 21:44:29 +01:00
pytest.ini Remove references to deprecated "py.test" 2018-06-04 16:36:02 -06:00
README.md Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00
requirements-docs.txt requirements.txt: best way to build on readthedocs 2018-01-30 15:17:03 -08:00
setup.py Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00
tox.ini Setup towncrier to generate release notes 2019-11-25 21:44:29 +01:00

<PROJECT_NAME>

Join the chat at https://gitter.im/ethereum/<REPO_NAME> Build Status PyPI version Python versions Docs build

<SHORT_DESCRIPTION>

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

Quickstart

pip install <PYPI_NAME>

Developer Setup

If you would like to hack on <REPO_NAME>, 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/<REPO_NAME>.git
cd <REPO_NAME>
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 <MODULE_NAME>/ tests/ -c "clear; flake8 <MODULE_NAME> 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 <REPO_NAME> failed'" ../tests ../<MODULE_NAME>

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"