-----BEGIN PGP SIGNED MESSAGE-----
On 02/26/2013 10:46 AM, Stephan Richter wrote:
> Even though, most ported packages are fully Python 3 compatible, they
> might depend on packages that are not ready to get a final release.
> Those two are:
> * zope.security 4.0.0 (pending PyPy support from Tres)
To be clear: what is missing is the pure-Python reference implementation
of the spacesuit proxies: without having that in place, passing the same
tests as the C version, and at 100% statement coverage, I'm not convinced
the Py3k port is "correct" (even though the C version passes all its
existing tests under Py3k). Essentially, I rushed the Py3k port in order
not to block others working on porting dependents.
I have relevant experience in the zope.proxy port that doing the
reference implementation actually uncovers bugs in the C implementation.
> * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.)
AFAIK, the remaining test failures on Py33 are largely spurious (doctest
repr issues, or else are pending the fork to use 'zodbpickle'.
> Any package that depends directly or indirectly on those two packages
> has an alpha release right now. Strictly speaking this is not
> necessary for any package not depending on ZODB (ZODB is special
> because the dep changes from ZODB3 to ZODB).
Packages which are still bleeding-edge themselves should be OK with
pinning non-final releases of their dependencies.
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/
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -