@@ -37,22 +37,23 @@ Developing
37
37
- Isolated ( if you have pipx installed): ``pipx install uv ``
38
38
39
39
- (Optional) Configure pre-commit for commit linter checks:
40
-
41
40
.. code-block :: bash
42
- pre-commit install
43
- pre-commit install --hook-type commit-msg
44
-
41
+
42
+ pre-commit install
43
+ pre-commit install --hook-type commit-msg
45
44
46
45
- Run from development tree. A virtual .venv will be created if you not have one
47
46
48
- - You can run using uv direct
49
- .. code-block :: bash
50
- uv run python-inspector --help
47
+ - You can run using uv direct
48
+ .. code-block :: bash
49
+
50
+ uv run python-inspector --help
51
51
52
- - Or if you have a virtual env activated do:
53
- .. code-block :: bash
54
- uv sync # One single time
55
- python-inspector --help
52
+ - Or if you have a virtual env activated do:
53
+ .. code-block :: bash
54
+
55
+ uv sync # One single time
56
+ python-inspector --help
56
57
57
58
58
59
Testing
@@ -61,21 +62,25 @@ Testing
61
62
- Run the tests. Tests have a special dependency group with their requirements for text exclusively:
62
63
63
64
.. code-block :: bash
64
- uv sync --group=test
65
+
66
+ uv sync --group=test
65
67
66
68
If you want to use Uv ( which enable possibility to use multiple python versions)
67
69
68
70
.. code-block :: bash
71
+
69
72
uv run -p 3.9 pytest -vvs
70
73
71
74
Or if you have a virtualenv activated with the deps installed
72
75
73
76
.. code-block :: bash
77
+
74
78
uv run -p 3.9 pytest -vvs
75
79
76
80
- These are live tests to regenerate the tests with updated data run::
77
81
78
- .. code-block :: bash
82
+ .. code-block :: shell
83
+
79
84
uv sync
80
85
PYINSP_REGEN_TEST_FIXTURES=yes uv run pytest -vvs
81
86
@@ -84,13 +89,13 @@ Documentation
84
89
-------------
85
90
86
91
.. code-block :: bash
92
+
87
93
uv sync --all-groups
88
94
hatch run validate-docs
89
95
90
96
91
-
92
97
Usage
93
- --------
98
+ -----
94
99
95
100
- Install with pip::
96
101
0 commit comments