burgholzer
commented
3 months ago I pushed a couple of changes here that should help to stir this in the right direction. First and foremost, I enabled Python 3.8 to 3.12 support. It should definitely be possible to support all these versions here. Then, I cleaned up the dependency mess a little bit and tried to identify suitable versions. I fixed whatever I could. However, I also left some things slightly broken and would ask you to please fix them. Most importantly, I updated all depenencies and some of the code to Qiskit 1.0. This broke some parts with QAOA, VQE, etc. There should be migration guides for all of these. So it is just a matter of time to fix the resulting errors.
The bigger thing, that is still unaddressed is concerning the warnings about invalid escape sequences in third party libraries. As far as I was able to tell, these concern DWave's libraries dimod + dwave-samplers and docplex. The main reason for this failure is that, since Python 3.11, such invalid escape sequences are no longer warnings, but SyntaxErrors. So this is really a fundamental flaw in these libraries. The appropriate thing to do is to raise issue in their repositories reporting the errors based on a minimal reproducible example. If a codebase is using ruff as a linter, there is even a check that prevents such sequences, see https://docs.astral.sh/ruff/rules/invalid-escape-sequence/. In most cases, you could probably fix those issues yourself and submit a PR to their repository. We would then wait for the respective PRs to be merged and a new release to be created. Then, we can use that release as a lowerbound here.
I also enabled the pre-commit bot for this repositore to reveal the respective warnings in PRs.
Pull request for obtaining a first mqt-toolkit-compatible release of the framework, adding documentation, managing libraries dependencies, updating code for supporting qiskit 1.0.