Python 3.12 and Qibo > 0.2.6

[alecandido]

It was blocked until now, mainly because of QUA (and also Qibosoq, but in qibosoq@main is already 3.12-ready, we simply did not bother to release).

This was also blocking Qibo releases supporting py3.12, and that's why we didn't catch #988 before.

However, I realized that there was a smarter way: just gate QUA to py<3.12, and not the whole Qibolab.

Closes #988

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.84%. Comparing base (34cb2fc) to head (3e0ed80).
Report is 28 commits behind head on 0.2.

Additional details and impacted files

@@            Coverage Diff             @@
##              0.2     #994      +/-   ##
==========================================
+ Coverage   42.83%   42.84%   +0.01%     
==========================================
  Files          80       80              
  Lines        5552     5553       +1     
==========================================
+ Hits         2378     2379       +1     
  Misses       3174     3174              

Flag	Coverage Δ
unittests	42.84% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[alecandido]

Btw, even in its latest (pre-)release, https://pypi.org/project/qm-qua/1.2.1a1/, qm-qua is imposing a bound to py<3.12. And I don't see any apparent reason for that, since new versions should be (almost completely) backward compatible.

@stavros11, could you ask them what's the motivation of this version lock?
It's a pure-python library, so they don't have to compile wheels for the new versions...

(unfortunately, it is not open-source, though I could manually inspect the dependencies from the wheel metadata...)

[stavros11]

@stavros11, could you ask them what's the motivation of this version lock? It's a pure-python library, so they don't have to compile wheels for the new versions...

(unfortunately, it is not open-source, though I could manually inspect the dependencies from the wheel metadata...)

I asked them a similar question about a year ago, when they first added such version lock, initially for py3.11. If you check on pypi qm-qua 1.1.1 did not have such constraints, while from 1.1.2 to 1.1.5 they restricted to py<3.11. At that time they responded that they had to do it because some of their dependencies (I don't know which) did not support py3.11. Then in qm-qua 1.1.6 they added 3.11 support because the dependencies were also updated. I am not sure about 3.12, but it could be a similar problem.