> Should the _Py-prefixed symbols be renamed, for example, from > > _PyUnicode_IsDecimalDigit > > to > > Py__Unicode_IsDecimalDigit I've replied to this and I'll reply again. When a C compiler is spotted that defines a conflicting symbol or that refuses to compile our code because of this, it's early enough to change this. > ? If so, we would then declare that all external symbols which begin with > "Py__" were part of the private API. The problem is that Py__ doesn't scream "internal" like "_Py" does. If we had to, I'd propose "_py". --Guido van Rossum (home page: http://www.python.org/~guido/)
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