Antoine Pitrou solipsis at pitrou.net
Mon Sep 12 08:03:30 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 Sun, 11 Sep 2016 04:37:58 -0400
Victor Stinner <victor.stinner at gmail.com> wrote:
> 
> For Python 3.7, I propose that we move all these private functions in
> separated header files, maybe Include/private/ or Include/core/, and
> not export them as part of the "regular API".

-1 from me.  There are reasons to rely on private stuff when necessary.

As long as private APIs are underscore-prefixed, people know what they
are risking by using them.

Regards

Antoine.

---

• 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 ]

---

More information about the Python-Dev mailing list