Remove tox support (#1219)

* Remove tox support

* Remove instances of tox

Author: Saransh-cpp

.gitignore

@@ -35,7 +35,6 @@ pip-delete-this-directory.txt
 
 # Unit test / coverage reports
 htmlcov/
-.tox/
 .coverage
 .coverage.*
 .cache

docs/contributing.rst

@@ -212,9 +212,12 @@ Test coverage
 
 Zarr maintains 100% test coverage under the latest Python stable release (currently
 Python 3.8). Both unit tests and docstring doctests are included when computing
-coverage. Running ``tox -e py38`` will automatically run the test suite with coverage
-and produce a coverage report. This should be 100% before code can be accepted into the
-main code base.
+coverage. Running::
+    
+    $ python -m pytest -v --cov=zarr --cov-config=.coveragerc zarr
+    
+will automatically run the test suite with coverage and produce a coverage report.
+This should be 100% before code can be accepted into the main code base.
 
 When submitting a pull request, coverage will also be collected across all supported
 Python versions via the Codecov service, and will be reported back within the pull
@@ -243,9 +246,10 @@ notes (``docs/release.rst``).
 
 The documentation can be built locally by running::
 
-    $ tox -e docs
+    $ cd docs
+    $ make clean; make html
 
-The resulting built documentation will be available in the ``.tox/docs/tmp/html`` folder.
+The resulting built documentation will be available in the ``docs/_build/html`` folder.
 
 Development best practices, policies and procedures
 ---------------------------------------------------

release.txt

@@ -1,4 +1,3 @@
-tox
 # version=x.x.x
 echo $version
 git tag -a v$version -m v$version

requirements_dev_optional.txt

@@ -13,7 +13,6 @@ types-redis
 types-setuptools
 pymongo==4.3.2
 # optional test requirements
-tox==3.26.0
 coverage
 flake8==5.0.4
 pytest-cov==4.0.0