You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @mhucka, I'd like to contribute to this issue. I see it's targeting Release 0.8.0. Which Cirq version should I target — 1.5.x or something newer? Also, is anyone actively working on this? Happy to pick it up if not.
Ideally we would want to support the latest version of Cirq; however, this is tricky because of the tangled dependencies between TensorFlow, TensorFlow Quantum, Keras, Cirq, qsim, and their transitive dependencies, and also because later versions of Cirq dropped support for Python 3.10 whereas TFQ still tries to support it. Let me work first on getting #1051 merged because that's going to change a bunch of dependency versions. Then we can assess the implications of raising Cirq's version.
Makes complete sense, thanks for the heads up! I'll keep an eye on #1051. Once that's merged and the team has decided how to handle the Python 3.10 / Cirq versioning, let me know — I'm still happy to help tackle the update
Activity
Kerbeccs commentedon May 2, 2026
Hi @mhucka, I'd like to contribute to this issue. I see it's targeting Release 0.8.0. Which Cirq version should I target — 1.5.x or something newer? Also, is anyone actively working on this? Happy to pick it up if not.
mhucka commentedon May 5, 2026
@Kerbeccs Thanks for your interest.
Ideally we would want to support the latest version of Cirq; however, this is tricky because of the tangled dependencies between TensorFlow, TensorFlow Quantum, Keras, Cirq, qsim, and their transitive dependencies, and also because later versions of Cirq dropped support for Python 3.10 whereas TFQ still tries to support it. Let me work first on getting #1051 merged because that's going to change a bunch of dependency versions. Then we can assess the implications of raising Cirq's version.
Kerbeccs commentedon May 24, 2026
Makes complete sense, thanks for the heads up! I'll keep an eye on #1051. Once that's merged and the team has decided how to handle the Python 3.10 / Cirq versioning, let me know — I'm still happy to help tackle the update