.. Ross Patterson's Blog imported post, created by `$ ./bin/rfc822-to-post` on Mar 15, 2021.

.. meta::
   :description: My experiences with Chameleon, testing compatibility and z3c.form
   :keywords: Plone, Zope

.. post:: Oct 07, 2010
   :tags: Plone, Zope
   :author: Ross Patterson
   :redirect:  @@redirect-to-uuid/b34dae498221e9fb0302e6884aa12643

####################
Trying out Chameleon
####################

    My experiences with Chameleon, testing compatibility and z3c.form

I'm about to upgrade a sizable client deployment to Plone 4 and wanted to see if I could switch to the `Chameleon <http://chameleon.repoze.org/>`_ template engine at the same time.  I'm recording things I found here:

Testing both with and without Chameleon
=======================================

For some add-ons of mine, I found it useful to be able to run the tests both with and without Chameleon.  It turns out to be `remarkably simple <https://dev.plone.org/collective/changeset/145722/>`_ with buildout.

Integrating cmf.pt and z3c.form
===============================

There are some gotchas when using both cmf.pt and z3c.form together.  You have to be sure to include z3c.ptcompat, which you can do with z3c.form's poorly named "extra" extras_require.  I did this in my project's setup.py by adding the following::


          install_requires=[
    ...
              'z3c.form[extra]<2.3dev',
    ...

Unfortunately, z3c.ptcompat uses an environment variable to switch on the use of Chameleon so you have to add the environment variable to the buildout instances and test runners::

    [instance]
    ...
    environment-vars =
      PREFER_Z3C_PT True
    ...
    [test]
    ...
    environment = testenv
    ...
    [testenv]
    PREFER_Z3C_PT = True
    


.. update:: Oct 07, 2010

   Imported from Plone on Mar 15, 2021.  The date for this update is the last
   modified date in Plone.