use make develop in contribution guide
--HG-- branch : parametrized-fixture-override
This commit is contained in:
parent
16bcfa749e
commit
24fe051803
|
@ -128,22 +128,18 @@ Preparing Pull Requests on Bitbucket
|
||||||
The primary development platform for pytest is BitBucket. You can find all
|
The primary development platform for pytest is BitBucket. You can find all
|
||||||
the issues there and submit your pull requests.
|
the issues there and submit your pull requests.
|
||||||
|
|
||||||
1. Fork the
|
#. Fork the
|
||||||
`pytest BitBucket repository <https://bitbucket.org/pytest-dev/pytest>`__. It's
|
`pytest BitBucket repository <https://bitbucket.org/pytest-dev/pytest>`__. It's
|
||||||
fine to use ``pytest`` as your fork repository name because it will live
|
fine to use ``pytest`` as your fork repository name because it will live
|
||||||
under your user.
|
under your user.
|
||||||
|
|
||||||
.. _virtualenvactivate:
|
#. Create a development environment
|
||||||
|
(will implicitly use http://www.virtualenv.org/en/latest/)::
|
||||||
|
|
||||||
2. Create and activate a fork-specific virtualenv
|
$ make develop
|
||||||
(http://www.virtualenv.org/en/latest/)::
|
$ source .env/bin/activate
|
||||||
|
|
||||||
$ virtualenv pytest-venv
|
#. Clone your fork locally using `Mercurial <http://mercurial.selenic.com/>`_
|
||||||
$ source pytest-venv/bin/activate
|
|
||||||
|
|
||||||
.. _checkout:
|
|
||||||
|
|
||||||
3. Clone your fork locally using `Mercurial <http://mercurial.selenic.com/>`_
|
|
||||||
(``hg``) and create a branch::
|
(``hg``) and create a branch::
|
||||||
|
|
||||||
$ hg clone ssh://hg@bitbucket.org/YOUR_BITBUCKET_USERNAME/pytest
|
$ hg clone ssh://hg@bitbucket.org/YOUR_BITBUCKET_USERNAME/pytest
|
||||||
|
@ -153,19 +149,20 @@ the issues there and submit your pull requests.
|
||||||
If you need some help with Mercurial, follow this quick start
|
If you need some help with Mercurial, follow this quick start
|
||||||
guide: http://mercurial.selenic.com/wiki/QuickStart
|
guide: http://mercurial.selenic.com/wiki/QuickStart
|
||||||
|
|
||||||
.. _testing-pytest:
|
#. Create a development environment
|
||||||
|
(will implicitly use http://www.virtualenv.org/en/latest/)::
|
||||||
|
|
||||||
4. You can now edit your local working copy. To test you need to
|
$ make develop
|
||||||
install the "tox" tool into your virtualenv::
|
$ source .env/bin/activate
|
||||||
|
|
||||||
$ pip install tox
|
#. You can now edit your local working copy.
|
||||||
|
|
||||||
You need to have Python 2.7 and 3.3 available in your system. Now
|
You need to have Python 2.7 and 3.4 available in your system. Now
|
||||||
running tests is as simple as issuing this command::
|
running tests is as simple as issuing this command::
|
||||||
|
|
||||||
$ python runtox.py -e py27,py33,flakes
|
$ python runtox.py -e py27,py34,flakes
|
||||||
|
|
||||||
This command will run tests via the "tox" tool against Python 2.7 and 3.3
|
This command will run tests via the "tox" tool against Python 2.7 and 3.4
|
||||||
and also perform "flakes" coding-style checks. ``runtox.py`` is
|
and also perform "flakes" coding-style checks. ``runtox.py`` is
|
||||||
a thin wrapper around ``tox`` which installs from a development package
|
a thin wrapper around ``tox`` which installs from a development package
|
||||||
index where newer (not yet released to pypi) versions of dependencies
|
index where newer (not yet released to pypi) versions of dependencies
|
||||||
|
@ -176,16 +173,16 @@ the issues there and submit your pull requests.
|
||||||
|
|
||||||
$ python runtox.py -e py27 -- --pdb
|
$ python runtox.py -e py27 -- --pdb
|
||||||
|
|
||||||
or to only run tests in a particular test module on py33::
|
or to only run tests in a particular test module on py34::
|
||||||
|
|
||||||
$ python runtox.py -e py33 -- testing/test_config.py
|
$ python runtox.py -e py34 -- testing/test_config.py
|
||||||
|
|
||||||
5. Commit and push once your tests pass and you are happy with your change(s)::
|
#. Commit and push once your tests pass and you are happy with your change(s)::
|
||||||
|
|
||||||
$ hg commit -m"<commit message>"
|
$ hg commit -m"<commit message>"
|
||||||
$ hg push -b .
|
$ hg push -b .
|
||||||
|
|
||||||
6. Finally, submit a pull request through the BitBucket website:
|
#. Finally, submit a pull request through the BitBucket website:
|
||||||
|
|
||||||
.. image:: img/pullrequest.png
|
.. image:: img/pullrequest.png
|
||||||
:width: 700px
|
:width: 700px
|
||||||
|
@ -214,5 +211,3 @@ original repository. If you insist on using git with bitbucket/hg you
|
||||||
may try `gitifyhg <https://github.com/buchuki/gitifyhg>`_ but are on your
|
may try `gitifyhg <https://github.com/buchuki/gitifyhg>`_ but are on your
|
||||||
own and need to submit pull requests through the respective platform,
|
own and need to submit pull requests through the respective platform,
|
||||||
nevertheless.
|
nevertheless.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue