@@ -97,7 +97,7 @@ the repository, you can do something like the following::
97
97
98
98
To verify that your development environment is working, you can run the unit tests::
99
99
100
- $ pytest -v zarr
100
+ $ python -m pytest -v zarr
101
101
102
102
Creating a branch
103
103
~~~~~~~~~~~~~~~~~
@@ -144,7 +144,7 @@ spec. The simplest way to run the unit tests is to activate your
144
144
development environment (see `creating a development environment `_ above)
145
145
and invoke::
146
146
147
- $ pytest -v zarr
147
+ $ python -m pytest -v zarr
148
148
149
149
Some tests require optional dependencies to be installed, otherwise
150
150
the tests will be skipped. To install all optional dependencies, run::
@@ -154,7 +154,7 @@ the tests will be skipped. To install all optional dependencies, run::
154
154
To also run the doctests within docstrings (requires optional
155
155
dependencies to be installed), run::
156
156
157
- $ pytest -v --doctest-plus zarr
157
+ $ python -m pytest -v --doctest-plus zarr
158
158
159
159
To run the doctests within the tutorial and storage spec (requires
160
160
optional dependencies to be installed), run::
@@ -186,7 +186,7 @@ All code must conform to the PEP8 standard. Regarding line length, lines up to 1
186
186
characters are allowed, although please try to keep under 90 wherever possible.
187
187
Conformance can be checked by running::
188
188
189
- $ flake8 --max-line-length=100 zarr
189
+ $ python -m flake8 --max-line-length=100 zarr
190
190
191
191
Test coverage
192
192
~~~~~~~~~~~~~
@@ -212,7 +212,7 @@ should run and pass as doctests under Python 3.8. To run doctests,
212
212
activate your development environment, install optional requirements,
213
213
and run::
214
214
215
- $ pytest -v --doctest-plus zarr
215
+ $ python -m pytest -v --doctest-plus zarr
216
216
217
217
Zarr uses Sphinx for documentation, hosted on readthedocs.org. Documentation is
218
218
written in the RestructuredText markup language (.rst files) in the ``docs `` folder.
0 commit comments