[Python-Dev] Deprecating C APIs (Use of PyArg_NoArgs()) (original) (raw)
M.-A. Lemburg mal@lemburg.com
Wed, 03 Apr 2002 15:22:08 +0200
- Previous message: [Python-Dev] Deprecating C APIs (Use of PyArg_NoArgs())
- Next message: [Python-Dev] Re: PEP 279
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 PYVERSIONHEX < 0x01060000_ _> > #if !defined(PyObjectDEL) > # define PyObjectDEL(x) free(x) > # define PyObjectDel(x) free(x) > #endif > > #endif
Why the PYVERSIONHEX 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/
- Previous message: [Python-Dev] Deprecating C APIs (Use of PyArg_NoArgs())
- Next message: [Python-Dev] Re: PEP 279
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]