jiuyuan
/
test_ok1
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

adapt contributing to new versioning and to python3.5 as latest.

This commit is contained in:
holger krekel 2015-09-21 14:04:30 +02:00
parent 65de43e67d
commit 0efcfeed17
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CONTRIBUTING.rst
View File

@ -151,7 +151,7 @@ but here is a simple overview:
$ git clone git@github.com:YOUR_GITHUB_USERNAME/pytest.git
$ cd pytest
$ git checkout pytest-2.7 # if you want to fix a bug for the pytest-2.7 series
$ git checkout 2.8.X # if you want to fix a bug for the pytest-2.8 series
$ git checkout master # if you want to add a feature bound for the next minor release
$ git branch your-branch-name # your feature/bugfix branch
@ -168,12 +168,12 @@ but here is a simple overview:
#. Run all the tests
You need to have Python 2.7 and 3.4 available in your system. Now
You need to have Python 2.7 and 3.5 available in your system. Now
running tests is as simple as issuing this command::
$ python runtox.py -e py27,py34,flakes
$ python runtox.py -e py27,py35,flakes
This command will run tests via the "tox" tool against Python 2.7 and 3.4
This command will run tests via the "tox" tool against Python 2.7 and 3.5
and also perform "flakes" coding-style checks. ``runtox.py`` is
a thin wrapper around ``tox`` which installs from a development package
index where newer (not yet released to pypi) versions of dependencies
@ -188,9 +188,9 @@ but here is a simple overview:
$ python runtox.py -e py27 -- --pdb
or to only run tests in a particular test module on py34::
or to only run tests in a particular test module on py35::
$ python runtox.py -e py34 -- testing/test_config.py
$ python runtox.py -e py35 -- testing/test_config.py
#. Commit and push once your tests pass and you are happy with your change(s)::