- 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 simpleflow on Github.
Clone your fork:
$ git clone email@example.com/botify-labs/simpleflow.git
Make your virtualenv and install dependencies. If you have virtualenv and virtualenvwrapper, run:
$ mkvirtualenv simpleflow $ cd simpleflow $ pip install -r requirements-dev.txt
- If you don’t have virtualenv and virtualenvwrapper, you can install both using virtualenv-burrito.
Git Branch Structure¶
simpleflow used to have a separated
devel branch but is now using only one, main branch
that contains what will be released in the next version. This branch is (hopefully) always stable.
Create a new local branch.
$ git checkout -b name-of-feature
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 should be tested and the docs should be updated.
- The pull request should work on Python 2.7 and PyPy. Use
toxto verify that it does.
- Submit a pull request to the
To run all the tests in your current virtual environment:
This is what Travis CI does on each environment.
If you want to simulate what Travis CI does, you can approach that by running a container from them:
$ ./script/test-travis python2.7 $ ./script/test-travis pypy
This can help you simulate locally what Travis CI would do. Be aware though that tests may fail
depending on your OS, so Travis CI is the reference gate for the project. For instance, installing
subprocess32 in a Pypy environment doesn’t work on Mac OSX.
To build docs:
$ invoke build_docs -b
-b (for “browse”) automatically opens up the docs in your browser after building.