CFFI 2.1 release with Python 3.15 support

[ngoldbaum]

There have been several nice new features merged since the last release. I'm particularly keen to see a release with Python 3.15 support.

Would you like to wait until 3.15.0rc1 comes out to ship a new release with Python 3.15 support? Or is building wheels using the beta releases and doing a release sooner OK?

[mattip]

@nitzmahone what do you think?

[nitzmahone]

Usually try to aim for releasing wheels sometime between b1-rc1, depending on what new Python features have affected us. As long as the folks that have been working on those features are reasonably confident that things are happy with the current state of 3.15, releasing anytime is okay by me.

I haven't had time to try hand-rolling a Py_TARGET_ABI3T extension under CFFI w/ 3.15.0b1+ yet, but given that the rest of the ecosystem is still catching up, it's probably not the end of the world if we need to quick-turn a followup release or two to address issues once setuptools (et al) are otherwise ready.

(EDIT) Ah, I see a bit of automatic support for it already landed last week

[ngoldbaum]

I haven't had time to try hand-rolling a Py_TARGET_ABI3T extension under CFFI w/ 3.15.0b1+ yet, but given that the rest of the ecosystem is still catching up, it's probably not the end of the world if we need to quick-turn a followup release or two to address issues once setuptools (et al) are otherwise ready.

I'm also around and will be working on this. I have a PR for cryptography open, for example: pyca/cryptography#15063

I'll mark that as mergeable once a release happens here.

Anyway it sounds like a v2.1 release is reasonable. I'll go ahead and prep a release PR.

[ngoldbaum]

@nitzmahone @mattip would one of you mind pushing a release-2.1 branch? I also think one of you will need to "push the button" to actually trigger a release.

[nitzmahone]

Will do! Given the number of build/test-related changes since the last release, I've kicked off a manual full CI run on main (including all the emulated arches) just to make sure everything's good. Assuming so, I'll create a 2.1 branch and kick off a release from there. I'm torn on whether to do a short 2.1.0b1- this project releases infrequently enough that I doubt there'd be much actual testing of pre-releases that would occur, so it's probably better to just do a full release and stand ready to quick-turn bugfixes as-needed.

[nitzmahone]

v2.1.0 has been released

[ngoldbaum]

Thanks for handling the parts that need a commit bit!

I'm hoping I can get a cryptography release shipped soon which will hopefully shake out issues downstream of cryptography if there are any. I'm also planning to look at abi3t support for PyNaCl and brotlicffi soonish.

[mattip]

Thanks @nitzmahone