-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSJroK3EjvBPtnXfVAQKeBwP/UlfTlCS3RgW5vuyaMjKbhQkL0d3nwOGr
NqYfLX6a0XRaroJzb9hPClzwyrkllQs6bLFoaFegTbi200+2Z3fG4z7vc1ywNBsu
rBIsyyQIN6kH7bqHqgqj0hDHgCNuobLz8m9R+Wodkafz4Jo49tDm60raUeHrKOvZ
TRIIUH5ZzVw=
=Q69C
-----END PGP SIGNATURE-----
_______________________________________________
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
