STINNER Victor <vstin...@python.org> added the comment:
I did'nt ask to remove the easter egg. I'm just asking to avoid the "new" name. In my experience, each time that a "new" thing happens, later we have to use "new extended", "new_v2" or worse name :-) Oh, if the name changes, please change it in 3.9 as well. Look at this amazing names of the 5 flavors of functions parsing a string: PyParser_ParseString() PyParser_ParseStringFlags() PyParser_ParseStringFlagsFilename() PyParser_ParseStringFlagsFilenameEx() <= public! PyParser_ParseStringObject() Same for parsing a file: PyParser_ParseFile() PyParser_ParseFileFlags() PyParser_ParseFileFlagsEx() <= public! PyParser_ParseFileObject() Or PyRun functions: PyRun_String() PyRun_AnyFile() PyRun_AnyFileEx() <= public! PyRun_AnyFileFlags() PyRun_SimpleString() PyRun_SimpleFile() PyRun_SimpleFileEx() <= public! PyRun_InteractiveOne() PyRun_InteractiveLoop() PyRun_File() PyRun_FileEx() <= public! PyRun_FileFlags() ceval.c: PyEval_EvalCode() PyEval_EvalCodeEx() <= public! _PyEval_EvalCodeWithName() _PyEval_EvalCode() I cannot count the number of "Ex" functions that we have :-) Py_Finalize() -> :Py_FinalizeEx() <= public! PyErr_Print() -> PyErr_PrintEx() <= public! PySys_SetArgv() -> PySys_SetArgvEx() <= public! PyErr_WarnEx() <= public! _PyBytes_FormatEx() _PyDict_MergeEx() _Py_DecodeLocaleEx(), _Py_EncodeLocaleEx() struct PyMemAllocatorEx _Py_DecodeUTF8Ex(), _Py_EncodeUTF8Ex() etc. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40939> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
