Guido van Rossum wrote: > > > > > I'd suggest to have a PEP which documents all C API changes > > > > or deprecations together with a short decsription of how to > > > > update old code. > > > > > > It shouldn't be a PEP (that's a *proposal*). It should be part of > > > the C API docs, possibly an appendix. > > > > I was thinking of an informational PEP -- mostly because PEPs > > are easily accessible and also simple to write (LaTeX is not > > everybody's friend ;-). > > Yeah, that's fine. Let whoever writes it decide on the format. :-) Good idea .. as long as someone does :-) > > True, but there are other instances where this was a problem > > in the past, e.g. > > > > #if PY_VERSION_HEX < 0x01060000 > > > > #if !defined(PyObject_DEL) > > # define PyObject_DEL(x) free(x) > > # define PyObject_Del(x) free(x) > > #endif > > > > #endif > > Why the PY_VERSION_HEX guard? Isn't the !defined() guard enough? Well, yes... this is more to document when the change happened. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
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