[Zope-dev] Current state of Python 3 migration

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/19/2012 01:34 PM, Marius Gedminas wrote:
> On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote:
>> On 12/19/2012 11:33 AM, Tres Seaver wrote:
>>> I spoke in error:  the zope.proxy extension is ported.  However,
>>> there is a chunk of 'proxy.h' which is *not* compiled when
>>> building the extension itself:  it is only compiled when included
>>> in another moduule.  That bit needs porting:  I will push it out
>>> this wee.
>> 
>> zope.proxy 4.1.0 released with that section Py3k compatible.  Note
>> that the cleanup required (enabling PyCapsule on Python 2.7)
>> requires that extensions built under Python 2.7 against a 4.0.x
>> version of the zope.proxy header must be rebuilt.
> 
> What happens if they're not?  Segfault?

I think a little more graceful than that:  you get a "module
initialization error", or something.



Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDSCVAACgkQ+gerLs4ltQ4U+ACfbz954FsE0jf5wfVtlVQ+zqbK
pgUAn1hXqxIbkrqVTK9+jDIwF2g/z2/2
=cK6Z
-----END PGP SIGNATURE-----