[issue46657] Add mimalloc memory allocator

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue46657> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44556] ctypes unittest crashes with libffi 3.4.2

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue44556> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40522] [subinterpreters] Get the current Python interpreter state from Thread Local Storage (autoTSSkey)

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue40522> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15751] [subinterpreters] Make the PyGILState API compatible with subinterpreters

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue15751> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40601] [C API] Hide static types from the limited C API

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue40601> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39511] [subinterpreters] Per-interpreter singletons (None, True, False, etc.)

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue39511> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40077] Convert static types to heap types: use PyType_FromSpec()

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue40077> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue1635741> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43112] SOABI on Linux does not distinguish between GNU libc and musl libc

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker <https://bugs.python.org/issue43112> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42380] Build windows binaries with MS VS2019 16.8+ / MSVC 19.28+

h-vetinari added the comment: PPS. Also, the compiler implementation reference uses 19.x for MSVC: https://en.cppreference.com/w/cpp/compiler_support, which was the link I was trying to make, now that I'm looking at it. -- ___ Python tracker

[issue42380] Build windows binaries with MS VS2019 16.8+ / MSVC 19.28+

h-vetinari added the comment: PS. > Judging from the link you posted to version numbering https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Internal_version_numbering the first line should have 'MSVC 14.28' the middle column title should be 'MS Visual Studio'. The wiki p

[issue42380] Build windows binaries with MS VS2019 16.8+ / MSVC 19.28+

h-vetinari added the comment: Hey Terry I had asked about this on discuss (https://discuss.python.org/t/toolchain-upgrade-on-windows/6377/2), and Steve provided some very valuable input. In particular, building with the newer VS (that supports C11) should stay ABI-compatible

[issue42380] Build windows binaries with MS VS2019 16.8+ / MSVC 19.28+

New submission from h-vetinari : While Visual Studio 16.8 (<-> MSVC 19.28) has _just_ been released, I think it would be worthwhile to consider upgrading the compiler toolchain that's used to build the CPython windows binaries, particularly before the release of 3.10. That's becaus