Lines Matching +full:tox +full:- +full:env
13 ----------------------------------
21 -------------------
27 -------------
31 the docs yourself via `tox -e docs` and make sure they're readable.
34 ---------------------
39 Expect some back-and-forth with regards to style and compliance of these
45 ----------------------------
50 - While logged into your GitHub account, navigate to the `oauth2client`
52 - Fork and clone the `oauth2client` repository to your GitHub account
54 - Clone your fork of `oauth2client` from your GitHub account to your
56 the destination as `hack-on-oauth2client`. For example:
60 $ git clone git@github.com:USERNAME/oauth2client.git hack-on-oauth2client
61 $ cd hack-on-oauth2client
73 - Create a virtualenv in which to install `oauth2client`:
76 $ cd ~/hack-on-oauth2client
77 $ virtualenv -ppython2.7 env
82 `--no-site-packages` flag to get a completely isolated environment.
85 `-p` flag to `virtualenv`. For example, `virtualenv -ppython2.7`
89 `~/hack-on-oauth2client/env` virtual environment you created above will be
91 follow literally, use the `export VENV=~/hack-on-oauth2client/env`
94 - Install `oauth2client` from the checkout into the virtualenv using
100 $ cd ~/hack-on-oauth2client
105 --------------
107 - To run all tests for `oauth2client` on a single Python version, run
111 - To run the full set of `oauth2client` tests on all platforms, install
112 [`tox`][2] into a system Python. The `tox` console script will be
114 `oauth2client` checkout root directory (it contains `tox.ini`),
115 invoke the `tox` console script. This will read the `tox.ini` file and
121 $ sudo pip install tox
122 $ cd ~/hack-on-oauth2client
123 $ tox
126 - In order to run the `pypy` environment (in `tox`) you'll need at
130 - **Note** that `django` related tests are turned off for Python 2.6
135 --------------------
137 - To run system tests you can execute:
140 $ tox -e system-tests
141 $ tox -e system-tests3
148 - System tests will be run against an actual project and so you'll need to
151 - `OAUTH2CLIENT_TEST_JSON_KEY_PATH`: The path to a service account JSON
156 - `OAUTH2CLIENT_TEST_P12_KEY_PATH`: The path to a service account
159 - `OAUTH2CLIENT_TEST_P12_KEY_EMAIL`: The service account email
161 - `OAUTH2CLIENT_TEST_USER_KEY_PATH`: The path to a JSON key file for a
166 - `OAUTH2CLIENT_TEST_USER_KEY_EMAIL`: The user account email
169 - Examples of these can be found in `scripts/local_test_setup.sample`. We
178 ------------------------------
183 - **If you are an individual writing original source code** and **you own
186 - **If you work for a company that wants to allow you to contribute your
193 [2]: https://tox.readthedocs.io/en/latest/
194 [3]: https://cloud.google.com/storage/docs/authentication#generating-a-private-key
195 [4]: https://developers.google.com/open-source/cla/individual
196 [5]: https://developers.google.com/open-source/cla/corporate
197 [6]: #contributor-license-agreements
199 [8]: https://help.github.com/articles/fork-a-repo/
200 [9]: #before-writing-code-file-an-issue
201 [10]: #fork-oauth2client
202 [11]: #include-tests
203 [12]: #make-the-pull-request
204 [13]: https://oauth2client.readthedocs.io/en/latest/#using-pypy
205 [14]: https://docs.djangoproject.com/en/1.7/faq/install/#what-python-version-can-i-use-with-django
206 [15]: https://docs.djangoproject.com/en/1.9/faq/install/#what-python-version-can-i-use-with-django
208 [GitCommitRules]: http://chris.beams.io/posts/git-commit/#seven-rules