Support for Python 3.12 #10887

jakelishman · 2023-09-22T12:35:00Z

This issue tracks various components that need to happen before we can be said to fully support Python 3.12. Notably, we will automatically have wheels available for Python 3.12 already, as since #10120 we've built our wheels against the stable Python C API, which means our released wheels should already be ABI compatible with Python 3.12. However, not all our dependencies will have pre-built wheels for Python 3.12.

Binary dependencies need to release 3.12 wheels

Give feedback

Numpy (as of 1.26.0)
Scipy (as of 1.11.2)
psutil (as of 5.9.4 it's released abi3 wheels)
Rustworkx (Release Python 3.12 wheels rustworkx#986)
Symengine (Build wheels for Python 3.12 symengine/symengine-wheels#11)
Options

Developer dependencies with problems

Give feedback

testtools fails to import due to the removal of distutils. Should be fixed in next release. (testtools fails to import with Python 3.12 testing-cabal/testtools#352, Reduce use of deprecated distutils module testing-cabal/testtools#353)
stestr complains that "run is not an 'stestr' command" with Python 3.12. This turned out to be a knock-on effect of the testtools problem above.
python-subunit uses deprecated datetime.datetime.utcnow, issuing warnings that fail our suite during collection. We can add skips for those warnings if necessary. See Remove use of deprecated datetime.datetime methods testing-cabal/subunit#71.
Options

Internal to Qiskit

Give feedback

We have problems with Numpy 1.25+ in some isometry code, but will need to support 1.26 for Python 3.12. See Incompatibility with Numpy 1.25 #10305, BUG: Multiply complex128 ufunc inconsistent with AVX2 numpy/numpy#24000.
We have problems with Scipy 1.11.0+ on Windows, most likely pre-existing. See Flaky CI tests with Scipy 1.11.0 on Windows Python 3.11 #10345.
Use of deprecated ast features. See Remove use of deprecated ast.Num for Python 3.12 #10886
Options

The text was updated successfully, but these errors were encountered:

Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: Qiskit#10887

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: #10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11.

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: #10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11. (cherry picked from commit 5a5c9e3) # Conflicts: # requirements.txt

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: #10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11. (cherry picked from commit 5a5c9e3)

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: #10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11. (cherry picked from commit 5a5c9e3) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: Qiskit#10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11.

* Add support for Python 3.12 Python 3.12.0 was released on 10-02-2023, this commit marks the start of support for Python 3.12 in Qiskit. It adds the supported Pythonv ersion in the package metadata and updates the CI configuration to run test jobs on Python 3.12 and build Python 3.12 wheels on release. Fixes: Qiskit/qiskit#10887 * Add release note * Avoid deprecated `datetime.datetime.utcnow()` usage In Python 3.12 `datetime.datetime.utcnow()` has been deprecated, being replaced by: `datetime.datetime.now(datetime.UTC)`. This commit updates the usage of `utcnow()` to follow the new convention. * Adjust UTC usage to support Python 3.8 The recommended alternative for using utcnow() in the deprecation warnings emitted by Python 3.12 are not compatible with Python 3.8. The datetime.UTC alias was not added to Python until Python 3.11. To ensure that the code is compatible with Python < 3.11 this commit updates all the usage of datetime.UTC to use datetime.timezone.utc instead, which is what datetime.UTC aliases to in Python >=3.11.

This was referenced Oct 1, 2023

ci: Add Python 3.12 to the testing symengine/symengine.py#451

Merged

Upgrade to Python 3.12 TheAlgorithms/Python#9576

Merged

xumingkuan mentioned this issue Oct 5, 2023

[CI] Fix incompatible Python version with symengine quantum-compiler/quartz#131

Merged

garrison mentioned this issue Oct 10, 2023

Add support for Python 3.12 Qiskit/qiskit-addon-cutting#429

Merged

mtreinish mentioned this issue Oct 11, 2023

Python 3.12 support Qiskit/qiskit-addon-mthree#191

Closed

mtreinish mentioned this issue Nov 16, 2023

Add support for Python 3.12 #11262

Merged

jakelishman closed this as completed in #11262 Nov 23, 2023

MaxleDrut mentioned this issue Jul 11, 2024

Add Python3.12 compatibility Alice-Bob-SW/qiskit-alice-bob-provider#39

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support for Python 3.12 #10887

Support for Python 3.12 #10887

jakelishman commented Sep 22, 2023 •

edited by mtreinish

Loading

Binary dependencies need to release 3.12 wheels

Developer dependencies with problems

Internal to Qiskit

Support for Python 3.12 #10887

Support for Python 3.12 #10887

Comments

jakelishman commented Sep 22, 2023 • edited by mtreinish Loading

Binary dependencies need to release 3.12 wheels

Developer dependencies with problems

Internal to Qiskit

jakelishman commented Sep 22, 2023 •

edited by mtreinish

Loading