[Python-Dev] Moving forward on the object memory API (original) (raw)
Martin v. Loewis martin@v.loewis.de
01 Apr 2002 17:19:25 +0200
- Previous message: [Python-Dev] Moving forward on the object memory API
- Next message: [Python-Dev] Re: PEP 285: Adding a bool type
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Peters <tim.one@comcast.net> writes:
> I'd be in favour of renaming them, thus actively breaking extension > modules that use them at compile time.
That would break every extension type written for 1.5.2; the relevant ones from Neil's random sampling are:
There are different levels of breakage, though: low: generates a warning when invoked middle: fails to compile high: compiles, but corrupts memory at run-time
If even the middle level is too much breakage, I'd be in favour of deprecating things in the low level: map them to a function that produces a warning when invoked.
Regards, Martin
- Previous message: [Python-Dev] Moving forward on the object memory API
- Next message: [Python-Dev] Re: PEP 285: Adding a bool type
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]