scnc
/
qiskit
mirror of https://github.com/Qiskit/qiskit.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qiskit/constraints.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

12 lines
605 B
Plaintext
Raw Normal View History

Temporarily pin `scipy<1.11` in CI (#10348) The newest Scipy on Windows seems to have caused a convergence error in some of the Weyl-chamber code. This pins Scipy temporarily while we resolve that issue.
2023-06-27 00:25:47 +08:00
# Scipy 1.11 seems to have caused an instability in the Weyl coordinates
# eigensystem code for one of the test cases. See
# https://github.com/Qiskit/qiskit-terra/issues/10345 for current details.
Add support for Python 3.12 (#11262) * 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.
2023-11-24 02:17:14 +08:00
scipy<1.11; python_version<'3.12'
Pin `z3-solver` on macOS VMs (#11408) We currently use macOS 11.7 images in our CI and CPython 3.8 for the all-optionals test run. `z3-solver` recently released 4.12.3.0, which upped the macOS platform version from 10.16 to 11.7. This in theory should be fine for our VM image, but the pre-built version of CPython 3.8 we have access to was built for an older macOS, so does not match a `macos_11_7_x86_64` platform tag, and forces us to build Z3 from source, often timing out the job. This should have no effect on user machines, which will be typically be using newer versions of Python, or will be able to install from source if required. This CI-only constraint can be relaxed when the version of CPython we use on the macOS VMs supports the 11.7 macOS API version.
2023-12-14 00:12:38 +08:00
# z3-solver from 4.12.3 onwards upped the minimum macOS API version for its
# wheels to 11.7. The Azure VM images contain pre-built CPythons, of which at
# least CPython 3.8 was compiled for an older macOS, so does not match a
# `macos_11_7` platform tag. This should be purely a CI artefact, and not
# affect local usage.
z3-solver==4.12.2.0; platform_system=="Darwin"