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?


Jim Fulton
Zope Corporation

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to