[Python-Dev] Python 3.7: remove all private C functions from the Python C API? (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Mon Sep 12 04:59:57 EDT 2016
- Previous message (by thread): [Python-Dev] Python 3.7: remove all private C functions from the Python C API?
- Next message (by thread): [Python-Dev] Python 3.7: remove all private C functions from the Python C API?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12.09.16 11:41, Victor Stinner wrote:
2016-09-12 8:23 GMT+02:00 Benjamin Peterson <benjamin at python.org>:
That seems like a good idea in abstract. However, the boundaries will have to be delineated. Many functions beginning Py are effectively part of the public API even for "well-behaved" 3rd-party extensions Oh ok, that's also what I expected. So we should be very careful. Maybe we can experiment building a few major C extensions like numpy to find such issues?
I think would be nice to create a test extension that uses all stable functions, build it with old Python versions and test if it works with new Python versions.
- Previous message (by thread): [Python-Dev] Python 3.7: remove all private C functions from the Python C API?
- Next message (by thread): [Python-Dev] Python 3.7: remove all private C functions from the Python C API?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]