docs: replace poetry with uv in docs build, use strict sphinx build

.github/workflows/build_and_test.yml

@@ -280,9 +280,14 @@ jobs:
     if: needs.check_changes.outputs.tket_or_workflow_changed == 'true' || needs.check_changes.outputs.pytket_or_workflow_changed == 'true'
     runs-on: ubuntu-24.04
     steps:
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+      with:
+          enable-cache: true
+          version: "0.10.9"
     - uses: actions/checkout@v6
       with: 
-        submodules: recursive
+        submodules: true
     - uses: extractions/setup-just@v3
       with:
         just-version: 1.5.0
@@ -355,12 +360,9 @@ jobs:
       if: github.event_name == 'pull_request' || github.event_name == 'workflow_dispatch'
       timeout-minutes: 20
       run: |
-        pip install poetry==2.1.4
-        poetry config virtualenvs.create false
         cd pytket/docs
-        poetry install
-        # just build-strict # https://github.com/quantinuum/tket/issues/2044
-        just build
+        just install-dev
+        just build-strict
     - name: Upload artifact
       if: github.event_name == 'pull_request' || github.event_name == 'workflow_dispatch'
       uses: actions/upload-artifact@v7

pytket/docs/README.md

@@ -20,15 +20,14 @@ cd pytket/docs
 
 The steps outlined below can be performed with the [just command runner](https://github.com/casey/just).
 
-## Install (requires a [poetry](https://python-poetry.org/) installation).
+## Install (requires a [uv](https://docs.astral.sh/uv/) installation).
 
-(use `just install-dev` to install a develop wheel of pytket)
+To install the dependencies needed for the local docs build, run
 
 ```shell
 just install
 ```
 
-use `just install-dev` to install a develop wheel of pytket
 
 ## Build the html
 

pytket/docs/extensions.md

@@ -36,9 +36,6 @@ A full list of available pytket backends is shown below.
 {py:class}`~pytket.extensions.pyquil.backends.forest.ForestBackend`
 \- A backend for running circuits on remote Rigetti devices.
 
-{py:class}`~pytket.extensions.aqt.backends.aqt.AQTBackend`[AQTBackend]
-\- Interface to an AQT device or simulator.
-
 {py:class}`~pytket.extensions.iqm.backends.iqm.IQMBackend`
 \- Interface to an IQM device or simulator.
 
@@ -66,9 +63,6 @@ A full list of available pytket backends is shown below.
 
 {py:class}`~pytket.extensions.pyquil.backends.forest.ForestStateBackend` - State-based interface to a Rigetti device.
 
-{py:class}`~pytket.extensions.projectq.backends.projectq_backend.ProjectQBackend`
-\- Backend for running statevector simulations on the ProjectQ simulator.
-
 {py:class}`~pytket.extensions.quest.backends.quest_backend.QuESTBackend` - Interface to the [QUEST simulator](https://quest.qtechtheory.org/docs/).
 
 ## Unitary Simulators
@@ -114,12 +108,10 @@ Use `QulacsBackend(result_type="density_matrix")`.
 :caption: 'Extensions:'
 :maxdepth: 0
 
-pytket-aqt <https://quantinuum.github.io/pytket-aqt/api/index.html>
 pytket-braket <https://docs.quantinuum.com/tket/extensions/pytket-braket>
 pytket-cirq <https://docs.quantinuum.com/tket/extensions/pytket-cirq>
 pytket-iqm <https://docs.quantinuum.com/tket/extensions/pytket-iqm>
 pytket-pennylane <https://docs.quantinuum.com/tket/extensions/pytket-pennylane>
-pytket-projectq <https://docs.quantinuum.com/tket/extensions/pytket-projectq>
 pytket-pyquil <https://docs.quantinuum.com/tket/extensions/pytket-pyquil>
 pytket-pysimplex <https://docs.quantinuum.com/tket/extensions/pytket-pysimplex>
 pytket-pyzx <https://docs.quantinuum.com/tket/extensions/pytket-pyzx>

pytket/docs/faqs.md

@@ -28,7 +28,7 @@ See the manual section on [unitary synthesis](https://docs.quantinuum.com/tket/u
 
 Q: How can I convert my qiskit {py:class}`qiskit.circuit.QuantumCircuit` to a pytket {py:class}`~.Circuit`?
 
-A: This can be achieved using the {external+pytket-qiskit:py:func}`pytket.extensions.qiskit.qiskit_to_tk` function from the [pytket-qiskit extension](https://docs.quantinuum.com/tket/extensions/pytket-qiskit/)
+A: This can be achieved using the `qiskit_to_tk` function from the [pytket-qiskit extension](https://docs.quantinuum.com/tket/extensions/pytket-qiskit/)
 
 ```
 from qiskit import QuantumCircuit
@@ -43,7 +43,7 @@ qc.cx(0, 1)
 tk_circ = qiskit_to_tk(qc)
 ```
 
-Conversion in the opposite direction can be accomplished using {external+pytket-qiskit:py:func}`pytket.extensions.qiskit.tk_to_qiskit`. In the case where there is no replacement for a pytket operation in qiskit the unsupported operation will be implemented in terms of the available gates.
+Conversion in the opposite direction can be accomplished using `qiskit_to_tk`. In the case where there is no replacement for a pytket operation in qiskit the unsupported operation will be implemented in terms of the available gates.
 
 Note here that `pytket` and `qiskit` use different qubit ordering conventions so care should be taken when
 converting between circuit formats and interpreting results.

pytket/docs/getting_started.md

@@ -120,7 +120,7 @@ compiled_circ = nairobi_device.get_compiled_circuit(circ)
 result = backend.run_circuit(compiled_circ, n_shots=100)
 ```
 
-Here the default compilation pass is applied by {external+pytket-qiskit:py:meth}`pytket.extensions.qiskit.IBMQBackend.get_compiled_circuit`. See [this page](https://docs.quantinuum.com/tket/extensions/pytket-qiskit/#default-compilation) for more details.
+Here the default compilation pass is applied by `IBMQBackend.get_compiled_circuit`. See [this page](https://docs.quantinuum.com/tket/extensions/pytket-qiskit/#default-compilation) for more details.
 
 As an alternative, We can experiment with constructing our own circuit compilation routines in pytket. Passes from the {py:mod}`pytket.passes` module can be applied individually or composed in sequence.
 See the section of the user manual on [circuit compilation](https://docs.quantinuum.com/tket/user-guide/manual/manual_compiler.html) and the corresponding [notebook example](https://docs.quantinuum.com/tket/user-guide/examples/circuit_compilation/compilation_example.html) for more.

pytket/docs/justfile

@@ -1,27 +1,26 @@
-install-dev:
-    poetry install
-    poetry run pip install ../.
-
-install:
-    poetry install
-    poetry run pip install -U pytket
-
 prepare:
     cp -R pytket-docs-theming/_static .
     cp pytket-docs-theming/conf.py .
 
-build *SPHINX_ARGS: prepare
-    VERSION=$(poetry run python -c "import pytket; print(pytket.__version__)") && \
-    poetry run sphinx-build {{SPHINX_ARGS}} -b html . build -D html_title="pytket v$VERSION API documentation"
+install: prepare
+    uv sync
+    uv pip install -U "pytket[ZX]"
+
+install-dev: prepare
+    uv sync
+    uv pip install ../.[ZX] -v
+
+build *SPHINX_ARGS:
+    VERSION=$(uv run python -c "import pytket; print(pytket.__version__)") && \
+    uv run sphinx-build {{SPHINX_ARGS}} -b html . build -D html_title="pytket v$VERSION API documentation"
 
 linkcheck: prepare
-    poetry run sphinx-build -W -b linkcheck . build
+    uv run sphinx-build -W -b linkcheck . build
 
 coverage: prepare
-    poetry run sphinx-build -W -v -b coverage . build/coverage
+    uv run sphinx-build -W -v -b coverage . build/coverage
 
-build-strict: prepare
-    VERSION=$(poetry run python -c "import pytket; print(pytket.__version__)") && \
+build-strict:
     just build -W # Fail on sphinx warnings
     just linkcheck
     just coverage
@@ -32,12 +31,13 @@ serve: build
 serve-debug:
     npm exec serve build
 
-cleanup:
-    # Clean up files generated by Sphinx
+clean:
+    # Clean up files generated by Sphinx build
     rm -rf jupyter_execute
     rm -rf .jupyter_cache
     rm -rf build
 
-    # Clean up config files in the event the build fails
+clean-env:
+    # Clean up the files copied over from the submodule
     rm -rf _static
     rm -f conf.py