Thank considering your contribution to DBGR. Any help or feedback is greatly appreciated.
Full documentation can be found on Read the Docs
If you want to develop debugger locally, there is an alternative installation process that will make this experience easier.
First, fork DBGR repository. Then you can clone the forked repo and create local environment:
$ git clone https://github.com/<your_username>/dbgr
$ cd dbgr
$ virtualenv env3.7 --python=python3.7
$ source env3.7/bin/activate
(env3.7) $ pip install -r requirements.txt -r requirements-dev.py
Tip
The process for setting up python 3.6 is the same, just use different python executable.
Now you can install DBGR from local directory:
$ source env3.7/bin/activate
(env3.7) $ pip install -e .
(env3.7) $ make test
This will run all unit-tests and generate coverage report. 100% test coverage is mandatory.
The file Makefile contains other commands that can be usefull when developing DBGR. Run make to see all the available commands.
(env3.7) $ make lint
DBGR user pylint with some lints disabled. See .pylintrc
for details. Score
of 10.0 is mandatory.
This documentation was build using Sphinx. To build it locally, run:
All new features and changes have to be documented.
(env3.7) $ make documentation
(env3.7) $ open open docs/build/html/index.html
These steps are mandatory only when preparing for release. Individual developers don't need to worry about them.
Run all tests, make sure they all pass and the code coverage is 100%.
Move appropriet changes from
# Unreleased
section inCHANGELOG.rst
to new version.Change version in
dbgr/meta.py
Build distribution, make sure there are no errors
(env3.7) $ make build
Tag new version on Github
Create new Github release
- Upload content of
dist
- Copy latest changes from
CHANGELOG.rst
to release description
- Upload content of
Upload content of
dist
to PyPi.(env3.7) $ make publish