December 2009 - Zope-Dev

Zope Toolkit - packages with zope.app dependencies
by Hanno Schlichting 29 Dec '09

29 Dec '09

Hi. I allowed myself to work on the Zope Toolkit over x-mas and make some decisions to get some progress ;-) The good news is that all our herculean efforts to unclutter the dependency structures have really payed off. Only very few zope.* packages still have dependencies on zope.app packages. I excluded those misbehaving packages from the ZTK to reflect this and noted them in a "unresolved-dependencies" option. The ZTK no longer contains any zope.app packages with one exception. There's a number of problematic packages, where I'd like some other opinions on how to proceed. zope.traversing It has a dependency on zope.app.publication. Given the central role of zope.traversing I allowed it and zope.app.publication to stay in the ZTK, but moved it to the under-review option. We have talked about refactoring the traversal and publication story in the past, without seeing any consensus on how to move forward with it. My feeling tells me, that a pure renaming of zope.app.publication to zope.publication or similar code reshuffling into other packages isn't really helpful in this case. ACTION: Until we see further progress on clarifying the semantics of traversal and publication, I'd leave zope.app.publication in the ZTK. zope.catalog and zope.intid Both of these have a dependency on zope.app.testing. Their tests heavily rely on a functional test setup with a ZODB and persistent data. They don't seem to need a publisher or a web server, though. ACTION: Remove them from the ZTK. Once their test setup no longer relies on zope.app.testing, they should move back into the ZTK. zope.file I think this package is just misnamed and should have been zope.app.file. It's a full blown content type implementation, with dependencies on zope.app.form, providing browser view code, browser menus and quite a bit of zope.app integration. It's test setup needs a full blown ZODB and publisher environment. ACTION: I'd remove this from the ZTK until someone is willing to refactor it to provide a minimal file implementation. zope.formlib and friends zope.formlib depends on zope.app.form which in turn depends on many zope.app packages. zope.html and zope.mimetype both depend on zope.formlib or zope.app.form. Various people myself included looked at the zope.formlib / zope.app.form split to see if it can be refactored in a sensible way. I think the conclusion has so far been: there's just no way. There isn't a sensible set of basic principles or interfaces in formlib, that can form a base for a higher level zope.app.form. All the packages using formlib today actually make use of the widgets in zope.app.form and thus basically on the entire functionality. With z3c.form we have another independent form library from the Zope community, which has seen at least as widespread if not more adoption. Preferring one over the other doesn't make much sense to me. ACTION: At this point I'd suggest to drop zope.formlib, zope.app.form and packages that depend on it from the ZTK. zope.testbrowser This package offers functional browser tests and consequently needs a way to set up a ZODB and publisher with some default application configuration. I don't see how this can be achieved without depending on a specific application environment like zope.app.appsetup or Zope2/App. Zope2 depends on the package and it makes sense to include it on the application server level - but not on a toolkit level for building frameworks. ACTION: I'd suggest to drop this package from the ZTK. Merry x-mas :) Hanno

7 17

Documentation on the Zope 2 release process
by Andreas Jung 29 Dec '09

29 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I started documenting the Zope 2 release process (Zope 2.12 only for now): svn+ssh://svn.zope.org/repos/main/zope2docs/trunk/maintenance/index.rst Hints and feedback appreciated. Andreas - -- ZOPYX Ltd. & Co KG \ zopyx group Charlottenstr. 37/1 \ The full-service network for your D-72070 Tübingen \ Python, Zope and Plone projects www.zopyx.com, info(a)zopyx.com \ www.zopyxgroup.com - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks6PwAACgkQCJIWIbr9KYyqTgCeLfknpgqeGLKpPM9Lj6aU57of kDgAoMUXidpW3eOfpIY8AQI7O5lFK8cM =Tr+l -----END PGP SIGNATURE-----

2 1

Zope Tests: 6 OK
by Zope Tests Summarizer 29 Dec '09

29 Dec '09

Summary of messages to the zope-tests list. Period Mon Dec 28 12:00:00 2009 UTC to Tue Dec 29 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Dec 28 20:55:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013281.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Dec 28 20:57:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013282.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 28 20:59:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013283.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 28 21:01:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013284.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 28 21:03:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013285.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 28 21:05:03 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013286.html

1 0

Avoid deprecation warnings in the testrunner
by Fabio Tranchitella 29 Dec '09

29 Dec '09

Hello, I think we should provide a zope.testing package which does not emit deprecation warnings while running the testrunner on other packages, otherwise there is no way to really understand why the package you are working on is using a deprecated API. I propose the patch attached to this message to zope.testing. It tries to avoid importing zope.testing.doctest unless it is really needed. In this way, developers can see the DeprecationWarning with the path of *their* code, and fix it, instead of receiving the DeprecationWarning because the testrunner imports zope.testing.doctest itself. Before applying the patch, running the tests on another package produced this output: ----------------------------------------------------------------------- .../zope/testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Running zope.testing.testrunner.layer.UnitTests tests: ... ----------------------------------------------------------------------- After applying my patch, I get this: ----------------------------------------------------------------------- .../zope/interface/tests/test_adapter.py:405: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Running zope.testing.testrunner.layer.UnitTests tests: ... ----------------------------------------------------------------------- Comments? Thanks, Fabio

4 19

PyPI access for zope.contenttype
by Fred Drake 28 Dec '09

28 Dec '09

Can someone set me up with PyPI privs for zope.contenttype? Thanks! -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller

2 2

Zope Tests: 6 OK
by Zope Tests Summarizer 28 Dec '09

28 Dec '09

Summary of messages to the zope-tests list. Period Sun Dec 27 12:00:00 2009 UTC to Mon Dec 28 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Dec 27 20:37:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013275.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Dec 27 20:39:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013276.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 27 20:41:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013277.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 27 20:43:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013278.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 27 20:45:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013279.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 27 20:47:05 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013280.html

1 0

Zope 2: circular import
by yuppie 28 Dec '09

28 Dec '09

Hi! I stumbled over a circular import in Zope 2. in DocumentTemplate.DT_Util: from ZPublisher.TaintedString import TaintedString this triggers ZPublisher.BaseRequest with: from AccessControl.ZopeSecurityPolicy import getRoles this triggers AccessControl.DTML with: from DocumentTemplate import DT_Util With try/except imports and the right import order this works, but it would be better to break up that circle. At first glance the solution is simple: TaintedString doesn't have any dependencies and is used by DocumentTemplate and ZPublisher. So it should be moved to a place where both modules can use it without triggering countless imports. But where would be a good place for TaintedString? It is too small to create a package just for that. In which existing package would it fit? Or should we just add a copy of TaintedString to DocumentTemplate? Any ideas? Cheers, Yuppie

2 2

Re: [Zope-dev] SVN: Zope/trunk/ Moved zope.formlib / zope.app.form integration into a separate package called five.formlib.
by Tres Seaver 28 Dec '09

28 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Log message for revision 107134: > Moved zope.formlib / zope.app.form integration into a separate package called five.formlib. YAY! You rock, Hanno. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks29uUACgkQ+gerLs4ltQ5PxgCfXATXRVia/zjPBdCejJUJqi9s +2UAnRh2weLA/U60QlLhivv+TDLxUsWZ =QuLv -----END PGP SIGNATURE-----

4 8

Re: [Zope-dev] Zope Toolkit - packages with zope.app dependencies
by Hanno Schlichting 27 Dec '09

27 Dec '09

On Sun, Dec 27, 2009 at 7:16 AM, Nikolay Kim <fafhrd91(a)gmail.com> wrote: >> zope.catalog and zope.intid > > i've just removed zope.app.testing dependency from zope.intid package > i need access to pypi package to make release, my id 'fafhrd' Awesome, that's exactly the constructive response I love to see :) Unfortunately I don't have PyPi access to these packages myself. Can someone give "fafhrd" and "hannosch" access rights, please? Thanks, Hanno

3 4

Re: [Zope-dev] Zope Toolkit - packages with zope.app dependencies
by Hanno Schlichting 27 Dec '09

27 Dec '09

On Sun, Dec 27, 2009 at 9:54 AM, Martin Aspeli <optilude+lists(a)gmail.com> wrote: > It sounds like it'd be possible to fix these test dependencies in a > different way. I agree that the ideal solution is to have a zope.intid > with more sane test dependencies. I'm not sure pre-emptive ejection > from the ZTK is the way to get there, though. It seems it worked out exactly as I had hoped for, thanks to Nikolay Kim. Once one of us gets PyPi permissions for zope.intid, it's back in :) Sorry, I'm not good at encouraging people to do something, I only know how to use a little stick ;) Hanno

1 0