RetroSearch Browse

Wed Feb 9 15:00:49 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-February/107965.html

2011/2/9 Mark Shannon <marks at dcs.gla.ac.uk>:
> OK, so UnicodeError_xxx is important for codecs, but surely this sort of
> argument could be made for lots of things.
> Don't forget that for each function added to the API,
> all other implementations have to support it forever.

The C-API is about the biggest implementation detail of CPython, so
no, they don't have to.

>
> Unfortunately, UnicodeError_xxx are not the only new functions.
>
> Various others have been added:
>
> int Py_EnterRecursiveCall(char *where)
> void Py_LeaveRecursiveCall()
> int Py_ReprEnter(PyObject *object)
> void Py_ReprLeave(PyObject *object)
>
> HotPyModule_GetFilenameObject
> HotPy_CompileStringExFlags
>
> and a few others.
>
> Individual functions are not the problem,
> I'm sure all of these can be justified,
> its lack of process and review that bothers me.

If they can be justified, what is the process lacking?

-- 
Regards,
Benjamin

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/107965.html below:

[Python-Dev] API bloat