On Friday, Dec 13, 2002, at 16:48 Europe/Amsterdam, Guido van Rossum wrote: >> The PyArg_Parse replacement I would like to do (for which I have had, >> unfortunately, absolutely no support up to now, and which I don't feel >> up to designing all by myself) could fix this with PEP298: it would >> use >> the locked buffer interface if available on the object, and release >> the >> locked buffer after your method returns. > > I can't give you much more than moral support. :-( > > It sounds like it would be a Big Change though; are you sure you're up > to this for Python 2.3? No, I don't think it'll happen before that time, there's oodles of MacOSX stuff I still want to do, and that'll keep me off the street for the time being. But if we have the process underway before 2.3 I hope I may be able to convince you that we should keep PyArg_Parse semantics as they are. -- Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman
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