On Thu, Aug 7, 2008 at 5:18 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > On Aug 7, 2008, at 5:09 AM, M.-A. Lemburg wrote: > >>>> Is it too late for that ? >>> >>> That kind of depends on how far other 3rd party projects are in >>> porting their extensions to Py3k, and how much they've bought into >>> these APIs. I recall that mechanically translating these APIs to >>> something else can easily introduce memory leaks. >> >> True, but isn't it better to go through that pain for a few extensions >> now and then have a proper C API to use in 3.1 ? Otherwise, we end >> up having to support those APIs for the whole lifetime >> of the 3.x branch. >> >> Note that those two APIs are not documented, so their use is not >> yet officially allowed. > > I'd prefer not introducing such instability this late in the beta processes, > but I agree that fixing it now will be better in the long term.
I see this as a sufficient endorsement. Marc-Andre, can you do this? -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
