-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/21/2012 09:18 PM, Sebastien Douche wrote: > On Sat, Dec 22, 2012 at 2:33 AM, Tres Seaver <tsea...@palladion.com> > wrote: >> I have addressed thses issues by: >> >> - - Releasing zope.security 3.8.5 with the correct header (still >> pinned). >> >> - - Releasing zope.security 3.9.0 with the zope.proxy requirement >> >= 4.1.0, and the correct header. > > Tres, is zope.security 3.9.0 compatible with Python 3.3? Still the > same errors:
No. I've done some work on the trunk toward the Py3k port, but is is not complete. I expect the 4.0 release to mark Py3k compatibility, along with related changes like PyPy support, Sphinx docs, 100% unit test coverage, and tox-driven tests for all supported Python versions. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDVLGEACgkQ+gerLs4ltQ6+QwCg18+H6564TtMyskQb1Fs0AA08 32AAn26b0I1L7YAIIuSy6wnMpKmuPcz6 =L9Bb -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )