I have to chime in here too
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.
On Tue, Jun 30, 2009 at 6:28 PM, Jim Fulton <j...@zope.com> 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?
> 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 )
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -