Kay Hayen

One thing I started to look at only, is how strings changed. This from 3.11 ``` typedef struct { PyASCIIObject _base; Py_ssize_t utf8_length; /* Number of bytes in utf8, excluding...

So, what we might be able to do there, is to check for compactness do that first, like they seem to do: ``` if (_PyLong_BothAreCompact(a, b)) { return _PyLong_CompactValue(a) -...

So, the string changes are probably next, might be easy to make once I find a good time slot for it. And then a long migration can be done without...

@bersbersbers thanks, that made my day ❤️

Actually 1.9 has bunch of changes aimed at 3.12 support, but it's not nearly complete yet. Passing the thread state around is e.g. part of the work that will allow...

@rupurt you are missing a verb. Check out my 3.11 post series and wait for a coming 3.12 post series and monitor that for whatever the question was intended to...

Thanks @KevinRodriguez777 for your kind comment. Let me state it clearly however, I am not alone in this, you are e.g. doing all you can to make things easier for...

There is progress there, I did the necessary changes to abstract the `long` repr changes, and I commented out, the bits we need from `str` to do in-place operations, those...

In my book, there are little reasons to use 3.12, I understand 3.11 gave a boost, but 3.12 was preparing for the GIL stuff, and actually looses single core performance...

Hm, the `libcupti.so.12` would appear to be from the OS, not sure why it was included, something went wrong there with the installer detection. It may of course be from...