Update contributing docs to reflect switch to Poetry (#59)

docs/contributing.md

@@ -16,72 +16,64 @@ git clone https://github.com/drhagen/tensora.git
 
 ## Installing from source
 
-Tensora uses pip as its dependency manager. Install the dependencies and dev dependencies, and then install Tensora in editable mode:
+Tensora uses Poetry as its packaging and dependency manager. In whatever Python environment you prefer, [install Poetry](https://python-poetry.org/docs/) and then use Poetry to install Tensora and its dependencies:
 
 ```shell
-pip install -r requirements.txt -r dev-requirements.txt
-pip install -e .
+pip install poetry
+poetry install
 ```
 
 ## Testing
 
 Tensora uses pytest to run the tests in the `tests/` directory. The test command is encapsulated with Nox:
 
 ```shell
-nox -s test test_numpy
+poetry run nox -s test test_taco test_numpy
 ```
 
 This will try to test with all compatible Python versions that `nox` can find. To run the tests with only a particular version, run something like this:
 
 ```shell
-nox -s test-3.10 test_numpy-3.10
+poetry run nox -s test-3.10 test_taco-3.10 test_numpy-3.10
 ```
 
-It is good to run the tests locally before making a PR, but it is not necessary to have all Python versions run. It is rare for a failure to appear in a single version, and the CI will catch it anyway. 
+It is good to run the tests locally before making a PR, but it is not necessary to have all Python versions run. It is rare for a failure to appear in a single version, and the CI will catch it anyway.
 
 ## Code quality
 
 Tensora uses Ruff to ensure a minimum standard of code quality. The code quality commands are encapsulated with Nox:
 
 ```shell
-nox -s fmt
-nox -s lint
+poetry run nox -s format
+poetry run nox -s lint
 ```
 
 ## Generating the docs
 
 Tensora uses MkDocs to generate HTML docs from Markdown. For development purposes, they can be served locally without needing to build them first:
 
 ```shell
-mkdocs serve
+poetry run mkdocs serve
 ```
 
 To deploy the current docs to GitHub Pages, Tensora uses the MkDocs `gh-deploy` command that builds the static site on the `gh-pages` branch, commits, and pushes to the origin:
 
 ```shell
-mkdocs gh-deploy
+poetry run mkdocs gh-deploy
 ```
 
 ## Making a release
 
 1. Bump
-    1. Increment version in `setup.py`
+    1. Increment version in `pyproject.toml`
     2. Commit with message "Bump version number to X.Y.Z"
     3. Push commit to GitHub
     4. Check [CI](https://github.com/drhagen/tensora/actions/workflows/ci.yml) to ensure all tests pass
 2. Tag
     1. Tag commit with "vX.Y.Z"
     2. Push tag to GitHub
-3. Build
-    1. Clear `dist/`
-    2. Run `python setup.py sdist`
-    3. Verify that sdist (`.tar.gz`) is in `dist/`
-4. Publish
-    1. Run `twine check dist/*`
-    2. Run `twine upload --repository testpypi dist/*`
-    3. Check [PyPI test server](https://test.pypi.org/project/tensora/) for good upload
-    4. Run `twine upload dist/*`
-    5. Check [PyPI](https://pypi.org/project/tensora/) for good upload
-5. Document
+    3. Wait for [build](https://github.com/drhagen/tensora/actions/workflows/release.yml) to finish
+    4. Check [PyPI](https://pypi.org/project/tensora/) for good upload
+3. Document
     1. Create [GitHub release](https://github.com/drhagen/tensora/releases) with name "Tensora X.Y.Z" and major changes in body
     2. If appropriate, deploy updated docs