1- # How to create a dev venv
1+ # Local development
22
3- If you have tox, you can run: ` tox -re venv ` , that will get you a ` .venv/ `
4- ready to go.
5-
6- If you don't have tox, you can run this (any python 3.6+ will do):
3+ Create a dev venv:
74
85``` shell
9- rm -rf .venv
10- /usr/bin/python3 -mvenv .venv
11- .venv/bin/pip install -U pip
12- .venv/bin/pip install -r requirements.txt -r tests/requirements.txt
13- .venv/bin/pip install -e .
6+ uv venv
7+ uv pip install -r requirements.txt -r tests/requirements.txt
8+ uv pip install -e .
149```
1510
1611You can then run ` portable-python ` from that venv:
@@ -24,10 +19,8 @@ You can then run `portable-python` from that venv:
2419# Run the tests
2520
2621If you have tox, just run: ` tox ` to run all the tests. You can also run:
27- - ` tox -e py39 ` to run with just one python version
22+ - ` tox -e py313 ` to run with just one python version
2823- ` tox -e style ` to check PEP8 formatting
29- - ` tox -r ` if you changed any ` requirements.txt ` (` -r ` is short for ` --recreate ` )
30- - ` tox -re py39 ` to recreate and run ` py39 ` only
3124- etc
3225
3326If you don't have tox, you can run the tests with: ` .venv/bin/pytest tests/ `
@@ -49,7 +42,7 @@ You can easily run `portable-python` in a debugger.
4942In PyCharm for example, you would simply browse to ` .venv/bin/portable-python `
5043then right-click and select "Debug portable-python".
5144You can then edit the build/run configuration in PyCharm, add some "Parameters" to it,
52- like for example ` build-report 3.10.5 ` , and then set breakpoints wherever you like.
45+ like for example ` build-report 3.13.2 ` , and then set breakpoints wherever you like.
5346
5447There is a ` --dryrun ` mode that can come in very handy for rapid iterations.
5548
@@ -71,5 +64,5 @@ docker run -it -v./:/src/ portable-python-jammy /bin/bash
7164Now inside docker, you run a build:
7265
7366``` shell
74- portable-python build 3.11.4
67+ portable-python build 3.13.2
7568```
0 commit comments