A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2016-September/146422.html below:

[Python-Dev] Python 3.7: remove all private C functions from the Python C API?

[Python-Dev] Python 3.7: remove all private C functions from the Python C API? [Python-Dev] Python 3.7: remove all private C functions from the Python C API?Antoine Pitrou solipsis at pitrou.net
Mon Sep 12 08:03:30 EDT 2016
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.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4