-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/18/2012 06:28 AM, Patrick Gerken wrote:
The first error (zope.app.appsetup) is due to deprecation warnings. I am not sure here. Is it normal that tests configure logs to output deprecations to stdout?
Is this the standard?
That is an oddball test -- it makes doctest assertions about the standar output of the server subprocess. I"ve tried to remediate the deprecation warnings which break the (over fragile. IMNSHO) assertions. Side note: the deprecation warnings are due to use of zope.interface.implements (and / or .implementsOnly, .classProvides). Those APIs cannot work on Python3, due to its different class initialization semantics, and so zope.interface 4.0.0 deprecates them in favor of the class decorators. zope.component.adapts is likewise broken under Python3, but there is not yet a release which actually deprecates it.
The zope.configuration errors are due to path issues with windows and linux. '/' just isn't a path separator for everyone. It looks like Tres is working on that.
I whacked a couple more moles[1] last night on that one. [1] http://en.wikipedia.org/wiki/Whac-A-Mole for those of you who postdate mechanical arcade games. :) Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+2PtIACgkQ+gerLs4ltQ4dmgCguSexksElYMmqWluVjm5hSv4P 82QAoMP12LMrl77DuhcKn6iU4Wbg2shA =qGyF -----END PGP SIGNATURE-----