On Tuesday 30 June 2009, 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.
Yes, I think testing with zope.release is a good way of doing this right now.
I tried to verify the steps:
1. Checkout zope.release
2. Run python bootstrap.py
3. Run ./bin/buildout -N
4. Run ./bin/generate-buildout
5. cd test
6. python ../bootstrap.py
7. ./bin/buildout -N
8. ./bin/test -vpc1
I am running the tests as I am writing this. So far I got one failure:
Traceback (most recent call last):
line 29, in <module>
ImportError: No module named pt
I'll report the full output when it is done.
> 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?
It is needed for the "latest-versions" script as this parses XML. I consider
lxml pretty much the standard tool to do XML in Python these days. Who is not
Having said that, "latest-versions" is not needed by everyone all the time. I
could live with putting it into an extra and not build the latest-versions
script by default.
Entrepreneur and Software Geek
Google me. "Zope Stephan Richter"
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -