Specify full test for dev env (switch to list)
[Imported from Trac: page Python3, version 10]
parent
e5b4c74e59
commit
2430240827
|
@ -8,7 +8,12 @@
|
||||||
|
|
||||||
## How to set up your development environment
|
## How to set up your development environment
|
||||||
|
|
||||||
We use [tox](https://tox.readthedocs.io/en/latest/) to standardize environments across developers and CI. So first install tox (globally, probably) and then in your Tahoe-LAFS working copy run `tox -e py36 --notest` to bootstrap the `py36` virtualenv. Then activate the environment with `source .tox/py36/bin/activate` or equivalent and run `trial allmydata.test.test_python3` as a smoke test.
|
We use [tox](https://tox.readthedocs.io/en/latest/) to standardize environments across developers and CI.
|
||||||
|
|
||||||
|
1. Install tox (globally, probably).
|
||||||
|
2. In your Tahoe-LAFS working copy, run `tox -e py36 --notest` to bootstrap the `py36` virtualenv.
|
||||||
|
3. Activate the environment with `source .tox/py36/bin/activate` or equivalent and run `trial allmydata.test.test_python3` as a smoke test.
|
||||||
|
4. `deactivate` the virtualenv (or switch shells) and run `tox -e py36` to exercise the whole suite.
|
||||||
|
|
||||||
## How to choose a module to port
|
## How to choose a module to port
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue