-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Fulton wrote:
> I should know this, but I don't. What is the recommended way to test
> changes to core ZTK packages to mitigate the risk that changes affect
> other packages? Is there a page somewhere with instructions?
>
> I tried using using zope.release. Building the trunk of zope.release
> with Python 2.4 and running the tests gives lots of test import errors
> and test failures. (Lots of tests want to import z3c.pt.) The tests
> hang when I try to build and run with Python 2.6.
>
> BTW, zope.release wants lxml, which is a real pain on Mac OS X and
> Centos 4. Does the ZTK really need to depend on lxml?
IMO, Any ZTK package should be testable via plain 'python2.{5,6}
setup.py test'. If that doesn't get the testing dependencies installed,
then they should be added.
There is a recipe for testing *other* packages which might be affected
by changes to the package-under-development:
http://pypi.python.org/pypi/z3c.recipe.compattest
I don't know how to supply the set of dependents to that recipe
(something in the buildout config file, I guess).
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.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKSlxt+gerLs4ltQ4RAgSeAKC41QMLihHrD9JcwmEmXeojL/4kMwCeLEfH
ltQDJ4vxrQQH3xBuj8w3uV0=
=7xZ4
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
