- PEP 8, when sensible.
- Test ruthlessly. Write docs for new features.
- Even more important than Test-Driven Development–Human-Driven Development.
Questions, Feature Requests, Bug Reports, and Feedback. . .¶
. . .should all be reported on the Github Issue Tracker .
Setting Up for Local Development¶
Fork webargs on Github.
$ git clone https://github.com/sloria/webargs.git $ cd webargs
Install development requirements. It is highly recommended that you use a virtualenv.
# After activating your virtualenv $ pip install -r dev-requirements.txt
Install webargs in develop mode.
$ pip install -e .
Git Branch Structure¶
Webargs abides by the following branching model:
- Current development branch. New features should branch off here.
- Current production release on PyPI.
- Maintenance branch for release
X.Y. Bug fixes should be sent to the most recent release branch.. The maintainer will forward-port the fix to
dev. Note: exceptions may be made for bug fixes that introduce large code changes.
Always make a new branch for your work, no matter how small. Also, do not put unrelated changes in the same branch or pull request. This makes it more difficult to merge your changes.
1. Create a new local branch.
# For a new feature $ git checkout -b name-of-feature dev # For a bugfix $ git checkout -b fix-something 1.2-line
2. Commit your changes. Write good commit messages.
$ git commit -m "Detailed commit message" $ git push origin name-of-feature
- Before submitting a pull request, check the following:
- If the pull request adds functionality, it is tested and the docs are updated.
- You’ve added yourself to
- Submit a pull request to
sloria:devor the appropriate maintenance branch. The Travis CI build must be passing before your pull request is merged.
To run all tests:
$ invoke test
To run tests on Python 2.7, 3.4, 3.5, and 3.6 virtual environments (must have each interpreter installed):
To install the packages for building the docs:
$ pip install -r docs/requirements.txt
To build the docs:
$ invoke docs -b
-b (for “browse”) automatically opens up the docs in your browser after building.