I have to chime in here too<br><br>lxml is a real pain and seems to be problematic to get a straightforward build for packages other than ZTK as well. I have had varying success building lxml even under ubuntu - success seems to be dependant on the type of build defined.<br>
<br>T<br><br><div class="gmail_quote">On Tue, Jun 30, 2009 at 6:28 PM, Jim Fulton <span dir="ltr"><<a href="mailto:jim@zope.com">jim@zope.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I should know this, but I don't. What is the recommended way to test<br>
changes to core ZTK packages to mitigate the risk that changes affect<br>
other packages? Is there a page somewhere with instructions?<br>
<br>
I tried using using zope.release. Building the trunk of zope.release<br>
with Python 2.4 and running the tests gives lots of test import errors<br>
and test failures. (Lots of tests want to import <a href="http://z3c.pt" target="_blank">z3c.pt</a>.) The tests<br>
hang when I try to build and run with Python 2.6.<br>
<br>
BTW, zope.release wants lxml, which is a real pain on Mac OS X and<br>
Centos 4. Does the ZTK really need to depend on lxml?<br>
<br>
Jim<br>
<br>
--<br>
Jim Fulton<br>
Zope Corporation<br>
<br>
<br>
_______________________________________________<br>
Zope-Dev maillist - <a href="mailto:Zope-Dev@zope.org">Zope-Dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/zope-dev" target="_blank">http://mail.zope.org/mailman/listinfo/zope-dev</a><br>
** No cross posts or HTML encoding! **<br>
(Related lists -<br>
<a href="http://mail.zope.org/mailman/listinfo/zope-announce" target="_blank">http://mail.zope.org/mailman/listinfo/zope-announce</a><br>
<a href="http://mail.zope.org/mailman/listinfo/zope" target="_blank">http://mail.zope.org/mailman/listinfo/zope</a> )<br>
</blockquote></div><br>