- Zope-Dev - Zope lists

Zope test layers, pytest, and test isolation
by Uli Fouquet 20 Apr '11

20 Apr '11

Hi there, Some of you might have noticed that some time ago the first version of `zope.pytest` was released: http://pypi.python.org/pypi/zope.pytest It's a try to make usage of `pytest` more comfortable in Zope-based environments. `zope.pytest` is mainly based on Martijns, Jan-Wijbrands, and Christian Klingers efforts. I put in some bits too. Right now we have a problem with pytest integration when it comes to ZCA setups: among other things `zope.pytest` offers a pytest-funcarg__ compatible function to automate ZCML based fixtures, i.e. it automatically adds setup and teardown functionality before/after test functions if requested by the test writer like this:: import my.project from zope.pytest import configure from zope.component import queryUtility def pytest_funcarg__config(request): return configure(request, my.project, 'ftesting.zcml') def test_myutil_registered(config): util = queryUtility( my.project.interfaces.ISomeIface, name = 'myutil', default = None) assert util is not None Here for test functions requiring an argument named ``config`` it is guaranteed that before the test function is run a ZCA initialization is performed based on the ZCML configuration given in the ``ftesting.zcml`` of `my.project`. This configuration is cached for the whole test session (the complete test run including all tests). If we assume that the used `ftesting.zcml` provides a named utility named ``myutil`` then the call to ``configure`` in the funcarg__-function should perform that registration and the 'myutil_registered' test should succeed. All that works very well -- in principle. The problem is: the `configure` function calls the registry setup before any real test is run and performs a teardown only after the last of all tests was run. And that leads to side-effects. In other words: all tests share the same global ZCA registrations and changes to the registrations in one test will affect other tests run thereafter. We have a lack of test isolation. Example:: import my.project from zope.pytest import configure from zope.component import queryUtility, provideUtility from zope.interface import Interface def pytest_funcarg__config(request): return configure(request, my.project, 'ftesting.zcml') def test_1(config): util = object() provideUtility(util, provides=Interface, name='a_util') def test_2(config): util = queryUtility(Interface, name='a_util', default=None) assert util is None def test_3(): util = queryUtility(Interface, name='a_util', default=None) assert util is None Here the second test will fail. Even worse, also the third test will fail, which does not require a ZCA setup at all. That's because the global registry is setup before all tests and not torn down before the last test was run. This behaviour is partly intentional: we do not want to setup/teardown the ZCA before/after single test functions as this would increase time consumed by test runs dramatically. Instead we want to reduce the number of ZCA setups/teardown as far as possible. We _could_ do a per testfunction setup/teardown by simply using a different test scope in `configure`. `pytest` offers three kinds of scope for that purpose: `session`, `module`, and `function`. `session` is the current default. Using `function` as scope we would get complete test isolation but pretty long lasting test runs. That could stop people from writing tests. Something we would like to avoid by all means. We could instead use `module` as default scope, so that all test functions inside a module would share one ZCA configuration (and for different test modules the setup would be performed from scratch). This might be a reasonable compromise. Test isolation of single tests inside a test module would of course be broken but one could say: if you want a fresh registry, just put your tests inside a new test module. With Zope test layers there might be a similar problem (each layer can create a global ZCA configuration that then will be shared amongst all applied test methods) but I think people are used to it and can cope with that specific test isolation breakage. A big advantage of test layers over `pytest` testing scopes might be that you can spread your tests associated to a certain layer over many files/modules/packages as you like and the setup/teardown will nevertheless only be performed once for each layer (well, normally at least). If you have one layer and that's enough for you, you will only have one ZCA-setup/teardown in the whole testrun. That's fast and certainly fits many real-world use-cases. Compared to Zope test layers I came to the conclusion that there is not much like this concept already in `pytest` and the behaviour of test layers can not easily be faked. `pytest` provides only the three mentioned scopes as kind of 'natural' layers. Spreading fixtures over many modules (as layers easily do) might contradict with the basic design goals of pytest and I am pretty sure that Holge Krekel wouldn't like it. Overall, we're now looking for a satisfying solution in terms of runtime and isolation. Some of the questions that arise: Would it make sense to bring the Zope layer concept into `pytest`? Are there already possibilities to mimic testlayer-like behaviour in `pytest` which we simply overlooked? Are there cheap/fast ways to cache/restore registry setups we hadn't had on the screen? Really fast setups/cache-restores could make even function-wise registrations a considerable thing. Would it simply be okay to use the 'module' scope for registration setups? Or do you have completely different ideas how to solve that issue? Any comments are really appreciated! Best regards, -- Uli

11 34

TestFixtures 1.9.2 Released!
by Chris Withers 20 Apr '11

20 Apr '11

Hi All, I'm happy to announce a new release of TestFixtures. This release adds a utcnow method to test_datetime that behaves identically to the now method: http://packages.python.org/testfixtures/api.html#testfixtures.tdatetime.utc… The package is on PyPI and a full list of all the links to docs, issue trackers and the like can be found here: http://www.simplistix.co.uk/software/python/testfixtures cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

1 0

zope-tests - FAILED: 9, OK: 76, UNKNOWN: 1
by Zope tests summarizer 20 Apr '11

20 Apr '11

This is the summary for test reports received on the zope-tests list between 2011-04-18 00:00:00 UTC and 2011-04-19 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] UNKNOWN : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.5 : Linux Zope-2.12-alltests Python-2.6.5 : Linux Zope-2.13 Python-2.6.5 : Linux Zope-2.13-alltests Python-2.6.5 : Linux Zope-trunk Python-2.6.5 : Linux Zope-trunk-alltests Python-2.6.5 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.coverage_py_265_32 [3] winbot / z3c.rml_py_265_32 [4] winbot / z3c.rml_py_265_32 [5] winbot / z3c.rml_py_265_32 [6] winbot / zc_buildout_dev py_254_win32 [7] winbot / zc_buildout_dev py_265_win32 [8] winbot / zc_buildout_dev py_265_win64 [9] winbot / zc_buildout_dev py_270_win32 [10] winbot / zc_buildout_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] UNKNOWN UNKNOWN : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 https://mail.zope.org/pipermail/zope-tests/2011-April/038523.html [2] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038496.html [3] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038521.html [4] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038494.html [5] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038490.html [6] FAILED winbot / zc_buildout_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038543.html [7] FAILED winbot / zc_buildout_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038544.html [8] FAILED winbot / zc_buildout_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038545.html [9] FAILED winbot / zc_buildout_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038546.html [10] FAILED winbot / zc_buildout_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038547.html

2 1

Repository cleanup: ZVSL licensed files?
by Michael Howitz 20 Apr '11

20 Apr '11

Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is "Zope Visible Source License, Version 1.0 (ZVSL)". Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436&view=rev Yours sincerely, -- Michael Howitz · mh(a)gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development

3 6

[Zope2] Multiline response headers causing problems for proxies.
by Laurence Rowe 19 Apr '11

19 Apr '11

When using response.appendHeader, Zope appends the new value following an ",\r\n\t" which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both Varnish [1] and Nginx [2] which may then mangle the header value. In fact the HTTP 1.0 spec notes that splitting over multiple lines in not recommended [3], though the HTTP 1.1 spec does not mention this explicitly, though it does say [4]: "Applications ought to follow "common form", where one is known or indicated, when generating HTTP constructs, since there might exist some implementations that fail to accept anything" Are there any objections to me applying the attached patch to Zope 2.13 and trunk? Laurence [1] http://www.varnish-cache.org/trac/ticket/905 [2] http://nginx.org/pipermail/nginx-devel/2011-April/000859.html [3] http://tools.ietf.org/html/rfc1945#section-4.2 [4] http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

2 3

zope-tests - FAILED: 7, OK: 72
by Zope tests summarizer 19 Apr '11

19 Apr '11

This is the summary for test reports received on the zope-tests list between 2011-04-17 00:00:00 UTC and 2011-04-18 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.5 : Linux Zope-2.12-alltests Python-2.6.5 : Linux Zope-2.13 Python-2.6.5 : Linux Zope-2.13-alltests Python-2.6.5 : Linux Zope-trunk Python-2.6.5 : Linux Zope-trunk-alltests Python-2.6.5 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.coverage_py_265_32 [2] winbot / z3c.rml_py_265_32 [3] winbot / zc_buildout_dev py_254_win32 [4] winbot / zc_buildout_dev py_265_win32 [5] winbot / zc_buildout_dev py_265_win64 [6] winbot / zc_buildout_dev py_270_win32 [7] winbot / zc_buildout_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038422.html [2] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038426.html [3] FAILED winbot / zc_buildout_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038450.html [4] FAILED winbot / zc_buildout_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038451.html [5] FAILED winbot / zc_buildout_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038452.html [6] FAILED winbot / zc_buildout_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038453.html [7] FAILED winbot / zc_buildout_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038454.html

1 0

zope-tests - FAILED: 11, OK: 80
by Zope tests summarizer 18 Apr '11

18 Apr '11

This is the summary for test reports received on the zope-tests list between 2011-04-16 00:00:00 UTC and 2011-04-17 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] Repository policy check found errors in 270 projects Total languishing bugs for zope2: 0 [2] Total languishing bugs for zope: 53 [3] Total languishing bugs for zopeapp: 2 [4] Total languishing bugs for zopetoolkit: 198 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.5 : Linux Zope-2.12-alltests Python-2.6.5 : Linux Zope-2.13 Python-2.6.5 : Linux Zope-2.13-alltests Python-2.6.5 : Linux Zope-trunk Python-2.6.5 : Linux Zope-trunk-alltests Python-2.6.5 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / z3c.coverage_py_265_32 [6] winbot / z3c.rml_py_265_32 [7] winbot / zc_buildout_dev py_254_win32 [8] winbot / zc_buildout_dev py_265_win32 [9] winbot / zc_buildout_dev py_265_win64 [10] winbot / zc_buildout_dev py_270_win32 [11] winbot / zc_buildout_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED Repository policy check found errors in 270 projects https://mail.zope.org/pipermail/zope-tests/2011-April/038323.html [2] FAILED Total languishing bugs for zope: 53 https://mail.zope.org/pipermail/zope-tests/2011-April/038307.html [3] FAILED Total languishing bugs for zopeapp: 2 https://mail.zope.org/pipermail/zope-tests/2011-April/038303.html [4] FAILED Total languishing bugs for zopetoolkit: 198 https://mail.zope.org/pipermail/zope-tests/2011-April/038305.html [5] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038337.html [6] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038335.html [7] FAILED winbot / zc_buildout_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038371.html [8] FAILED winbot / zc_buildout_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038372.html [9] FAILED winbot / zc_buildout_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038373.html [10] FAILED winbot / zc_buildout_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038374.html [11] FAILED winbot / zc_buildout_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038375.html

1 0

CatalogPathAwareness and zope.lifecycle
by Sascha Welter 17 Apr '11

17 Apr '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Zope Developers, I've asked about this on the zope@ list, without getting any replies. Talking about it in #zope, I decided that maybe I will have to ask here from another point of view. As I was testing moving a big, old application to Zope 2.13, I was greeted with the following error: (...) from Products.ZCatalog.CatalogPathAwareness import CatalogPathAware ImportError: cannot import name CatalogPathAware Looking at the code informs me that CatalogPathAwareness is deprecated. I since noticed that apart from the depreciation, also the "emtpy" class CatalogPathAware(CatalogAware) has been removed from CatalogPathAwareness.py. The depreciation message points to zope.lifecycleevent. Looking at http://pypi.python.org/pypi/zope.lifecycleevent I see some examples about calling those notify() events, but nothing that would tell me how to replace CatalogPathAware with this stuff. Googling for [CatalogPathAware zope.lifecycleevent] does not give me anything besides some SVN commit messages. So, anybody have some examples of doing this, please? Specifically an example for replacing CatalogPathAware with zope.lifecycleevent. Since this is what the depreciation message talks about, it's been done many times over and should be well documented, right? I also hope that developers are aware that this change involves changing the base classes that classes in production systems out there are based on. I assume this kind of thing has been discussed and the decision has been taken on judging backwards compatibility vs. the benefits of doing this? (Personally I don't know those benefits, but I'm open to learn. I'm also open to help if there is any work involved, I'm planning to give back more to the zope community in the near future.) Thank you very much, Regards, Sascha -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) iD8DBQFNqBeEpYOq9ODq/IoRAr8UAKCmziFbjoJ/rD+jOqycMnzyCjrPngCfQFoP UOqcNboJ0XMuX3z9sBM6z2o= =3aWj -----END PGP SIGNATURE-----

5 13

fanstatic and preprocessors
by Wolfgang Schnerring 17 Apr '11

17 Apr '11

Hi, is this the right place to ask stuff about fanstatic? Unfortunately I haven't had the opportunity to have a proper look at fanstatic (yet!), but I've just been reading about SASS and CoffeeScript, which are preprocessors/compilers for CSS and JavaScript. So I wondered whether it is within fanstatic's scope that one could feasibly write a plugin to support something like this. Something like, I drop a foo.coffee file somewhere and it would be run through the CoffeeScript compiler, probably cached, and served to clients as foo.js. (This thought has been triggered by what Rails is doing right now[1] which is powered by their equivalent resource manager[2].) Wolfgang [1] http://www.rubyinside.com/rails-3-1-adopts-coffeescript-jquery-sass-and-con… [2] https://github.com/sstephenson/sprockets

3 2

zope-tests - FAILED: 8, OK: 64, UNKNOWN: 1
by Zope tests summarizer 17 Apr '11

17 Apr '11

This is the summary for test reports received on the zope-tests list between 2011-04-15 00:00:00 UTC and 2011-04-16 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] UNKNOWN : Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [2] ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.5 : Linux Zope-2.12-alltests Python-2.6.5 : Linux Zope-2.13 Python-2.6.5 : Linux Zope-2.13-alltests Python-2.6.5 : Linux Zope-trunk Python-2.6.5 : Linux Zope-trunk-alltests Python-2.6.5 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [3] winbot / z3c.coverage_py_265_32 [4] winbot / z3c.rml_py_265_32 [5] winbot / zc_buildout_dev py_254_win32 [6] winbot / zc_buildout_dev py_265_win32 [7] winbot / zc_buildout_dev py_265_win64 [8] winbot / zc_buildout_dev py_270_win32 [9] winbot / zc_buildout_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx https://mail.zope.org/pipermail/zope-tests/2011-April/038272.html [2] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-April/038295.html [3] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038253.html [4] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/038251.html [5] FAILED winbot / zc_buildout_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038287.html [6] FAILED winbot / zc_buildout_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038288.html [7] FAILED winbot / zc_buildout_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038289.html [8] FAILED winbot / zc_buildout_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038290.html [9] FAILED winbot / zc_buildout_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038291.html

1 0