[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 <https://bugs.python.org/issue42380> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 page was refactored quite extensively it seems, this is what I had been referring to: https://en.wikipedia.org/w/index.php?title=Microsoft_Visual_C%2B%2B=997067123. But I'll happily admit that I don't understand the reasons behind (the differences between) the various version numbers: MSVC++, _MSC_VER, etc. -- ___ Python tracker <https://bugs.python.org/issue42380> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 with everything that has been built on Visual Studio 2015, 2017 and 2019: > This is different from all previous Visual C++ versions, as they each had > their own distinct runtime files, not shared with other versions. (from https://docs.microsoft.com/en-gb/cpp/windows/universal-crt-deployment?view=msvc-160=vs-2019), due to the way the (now-)universal runtime is designed. Thanks -- ___ Python tracker <https://bugs.python.org/issue42380> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 because many libraries (e.g. numpy/scipy) are stuck to the same compilers as CPython for ABI-compatibility, and generally, MSVC is by far the lowest common denominator in terms of C/C++ compliance, cf. https://github.com/scipy/scipy/blob/master/doc/source/toolchain.rst For example, dropping python 3.6 support in scipy should finally enable them to use C++14/C++17, since python 3.7+ is built with Visual Studio 15.7, which has essentially complete support, cf. https://en.cppreference.com/w/cpp/compiler_support & https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B#Internal_version_numbering. However (& as far as I can tell), the windows compiler version for CPython hasn't moved since the release of 3.7, cf. https://pythondev.readthedocs.io/windows.html#python-and-visual-studio-version-matrix (I know that's not an official page, but vstinner can hardly be considered a questionable source), and every release without upgrading the toolchain means another year of waiting for the ecosystem to unlock more modern C/C++. The reason why Visual Studio 16.8 is particularly interesting, is that MS has for a very long time not paid attention to C compliance, and only recently completed C99 support, with C11/C17 following in 16.8 (though as of yet without optional aspects of the standard like atomics, threading, VLAs, complex types, etc.), cf. https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/. Looking at the table from https://github.com/scipy/scipy/blob/master/doc/source/toolchain.rst, it would be cool if we could add the last line as follows === == === CPython MS Visual C++C Standard === == === 2.7, 3.0, 3.1, 3.2 9.0 C90 3.3, 3.410.0 C90 & some of C99 3.5, 3.614.0 C90 & most of C99 3.7 15.7 C90 & most of C99 3.8 15.7 C90 & most of C99 3.9 15.7 C90 & most of C99 3.1016.8 C99, C11*, C17 === == === * [comment about lack of C11 optionals] -- components: Windows messages: 381167 nosy: h-vetinari, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Build windows binaries with MS VS2019 16.8+ / MSVC 19.28+ type: enhancement versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue42380> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
