[Zope-dev] C-extension in zope.i18nmessageid

[Tres Seaver]

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

Jim Fulton wrote:
> On Dec 12, 2008, at 6:28 AM, Malthe Borch wrote:
> 
>> I've branched out this package and removed the C-extension. It's not
>> documented in the package why a C-extension is needed or  
>> alternatively,
>> what it benefits.
>>
>> If there are no objections, I will merge this into trunk shortly.
> 
> 
> I object. Please drop it.

I'd rather not drop it:  can we (today) justify the need for the C
extension?  If nothing else, that explanation needs to be added to the
package docs.  If the justification is "support the model of untrusted
code", could we not make the extension optional, and let folks who don't
have that use case get by without needing to pay the price?  For that
matter, who actually has the use case in Z3 land?  I don't know of *any*
deployed applications which use persistent code, and therefore which
need to worry about the problem.

Certainly nothing in Zope2 land uses space suits.


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.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJUDBw+gerLs4ltQ4RAhLuAJ9QUhPsCaVTOZAX0z+WEO1ojutKowCgvhUO
0gEhYrnEYAVzaVh610zgH3k=
=AtJt
-----END PGP SIGNATURE-----