Support Python 3.12 and bump rustworkx to 0.13.2

[IvanIsCoding]

Start the work to support #986:

• Bump PyO3 to 0.19.2 to support Python 3.12
• Add CI tests with Python 3.12 release candidate
• Update cibuildwheel to 2.16.1, which should build 3.12 wheels

Because this updates PyO3, I think it should trigger a minor version bump to 0.13.2. In the release notes, we can be clear this has little to no change for 0.13.1 users running Python 3.11 or earlier.

[coveralls]

Pull Request Test Coverage Report for Build 6392250583

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 96.415%

---

Files with Coverage Reduction	New Missed Lines	%
src/connectivity/mod.rs	2	96.51%

Totals
Change from base Build 5703070093:	0.03%
Covered Lines:	15009
Relevant Lines:	15567

---

💛 - Coveralls

[auvipy]

Should we consider dropping python 3.7 from CI beside adding python 3.12?

[IvanIsCoding]

Should we consider dropping python 3.7 from CI beside adding python 3.12?

No, we supported 3.7 in the 0.13.x series and we’ll keep supporting it. It’s already dropped for 0.14 and onwards

[mtreinish]

This LGTM, two questions inline but nothing major. The other thing is we probably need to do a cargo build and update the Cargo.lock because rustworkx and rustworkx-core are still at 0.13.1 in the lock file. The other thing is do you want to tag this PR as the 0.13.2, if so we probably should include a release note that notes that this release adds preliminary 3.12 support on top of 0.13.1.

[mtreinish]

I assume we'll have to wait a little bit for the default gha image to get 3.12.0.

[IvanIsCoding]

It's not in https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json, but the ABI should be identical to the released one

[IvanIsCoding]

This LGTM, two questions inline but nothing major. The other thing is we probably need to do a cargo build and update the Cargo.lock because rustworkx and rustworkx-core are still at 0.13.1 in the lock file. The other thing is do you want to tag this PR as the 0.13.2, if so we probably should include a release note that notes that this release adds preliminary 3.12 support on top of 0.13.1.

I added a very brief release note for 0.13.2. So I think we should be able to tag this with 0.13.2 for the release

[mtreinish]

LGTM, thanks for the quick updates

[mtreinish]

Oh, actually before we release this we'll need to update cibuildwheel in wheel builds to a newer version that includes 3.12 support

[IvanIsCoding]

Oh, actually before we release this we'll need to update cibuildwheel in wheel builds to a newer version that includes 3.12 support

Can you tag this commit as 0.13.2? I don't have the permission