feat(python): Support Python 3.12 (#394)

* feat(python): Support Python 3.12

* clippy

Author: MarquessV

.github/workflows/release-python.yml

@@ -30,7 +30,7 @@ jobs:
       CXXFLAGS: "-std=c++11 -stdlib=libc++"
     strategy:
       matrix:
-        python-version: ['3.8', '3.9', '3.10', '3.11']
+        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-python@v4
@@ -69,7 +69,7 @@ jobs:
       CXXFLAGS: "-std=c++11"
     strategy:
       matrix:
-        python-version: ['3.8', '3.9', '3.10', '3.11']
+        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
         target: [x86_64, aarch64]
     steps:
     - uses: actions/checkout@v2
@@ -104,7 +104,7 @@ jobs:
     needs: [is-python-release, should-publish-wheels]
     strategy: 
       matrix: 
-        python-version: ['3.8', '3.9', '3.10', '3.11'] 
+        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
         target: [x64] 
     steps: 
       - uses: actions/checkout@v2 
@@ -149,7 +149,7 @@ jobs:
         default: true
     - uses: actions/setup-python@v4
       with:
-        python-version: '3.11'
+        python-version: '3.12'
     - name: Install protoc
       uses: arduino/setup-protoc@v1
       with:

Cargo.lock

@@ -15,19 +15,19 @@ tokio = "1.24.2"
 # be a `quil-py` tag and should match the version used in `crates/python/pyproject.toml`
 # The version must also be specified in order to publish to crates.io. Cargo enforces
 # that the specified version is the same as the version in the git repository.
-quil-rs = { version = "0.22.0", git = "https://github.com/rigetti/quil-rs", tag = "quil-py/v0.6.0" }
+quil-rs = { version = "0.22.0", git = "https://github.com/rigetti/quil-rs", tag = "quil-py/v0.6.1" }
 
 # ndarray is used by the `qcs` crate, but it is also used in the `python` crate via a
 # re-export through the numpy crate. They should be updated as a pair to keep both
 # crates' versions of ndarray in sync.
 # Similarly, pyo3 packages (`numpy`, `rigetti-pyo3`, `pyo3*`) track versions together
 # and need to be updated together.
 ndarray = { version = "0.15.6", features = ["serde"] }
-numpy = "0.19"
-pyo3 = "0.19.2"
-pyo3-asyncio = { version = "0.19", features = ["tokio-runtime"] }
-pyo3-build-config = "0.19.2"
-rigetti-pyo3 = { version = "0.2.0", features = ["complex"] }
+numpy = "0.20.0"
+pyo3 = "0.20.0"
+pyo3-asyncio = { version = "0.20", features = ["tokio-runtime"] }
+pyo3-build-config = "0.20.0"
+rigetti-pyo3 = { version = "0.3.0", features = ["complex"] }
 
 # The primary intent of these options is to reduce the binary size for Python wheels
 # since PyPi has limits on how much storage a project can use.

Cargo.toml

@@ -282,7 +282,9 @@ impl<'a> Execution<'a> {
                 job_handle.readout_map(),
                 &response.readout_values,
             )),
-            duration: Some(response.execution_duration_microseconds).map(Duration::from_micros),
+            duration: Some(Duration::from_micros(
+                response.execution_duration_microseconds,
+            )),
         })
     }
 

crates/lib/src/qpu/execution.rs

@@ -20,7 +20,7 @@ classifiers = [
   "Programming Language :: Python :: 3.11",
   "Operating System :: OS Independent",
 ]
-dependencies = ["quil==0.6.0"]
+dependencies = ["quil==0.6.1"]
 
 # PEP 621 specifies the [project] table as the source for project metadata. However, Poetry only supports [tool.poetry]
 # We can remove this table once this issue is resolved: https://github.com/python-poetry/poetry/issues/3332