<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
On 03/18/2011 11:20 AM, Jesus Cea wrote:<br>
<blockquote cite="mid:4D83A262.5070503@jcea.es" type="cite">
<pre wrap="">I kind of remember doing this change myself. Since no 2.8 is planned, it
seemed sensible to mark PyCObject as a py3k warning.
</pre>
</blockquote>
<br>
It's all fine by me, and yeah I think you did the change. I'm sure
it wasn't me.<br>
<br>
<blockquote cite="mid:4D83A262.5070503@jcea.es" type="cite">
<pre wrap="">PS: I am the maintainer of (externally developed lib) bsddb, but the
2.7.0 behaviour actually broke some other extensions out there (when
used with warnings active). Details in the tracker, somewhere. I am
offline now, can't use the browser.
</pre>
</blockquote>
<br>
My point in bringing up bsddb was that it was the only remaining use
of CObject that shipped with Python 2.7. Yes, certainly there were
externally-maintained extensions that went to pieces when
PyCObject_FromVoidPtr() started returning NULL. But internally, 2.7
switched entirely to capsules, except for bsddb.<br>
<br>
Cheers,<br>
<br>
<br>
<i>larry</i><br>
</body>
</html>