- Zope-Dev - Zope lists

[labo] Disparition de nss3-1 & nss3-2
by Sebastien Douche 05 Mar '09

05 Mar '09

Pour rappel il existait nss3-{1,2,3] pour tester les corrections de bugs en 3.4 et 3.5. Comme nous développons plus la 3.4 (et que j'ai besoin de machines), j'ai récupéré les deux premières. -- Sebastien Douche <sdouche(a)gmail.com>

1 1

Zope Tests: 6 OK
by Zope Tests Summarizer 05 Mar '09

05 Mar '09

Summary of messages to the zope-tests list. Period Wed Mar 4 12:00:00 2009 UTC to Thu Mar 5 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: Wed Mar 4 20:25:30 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011229.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 4 20:27:34 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011230.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 4 20:29:34 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011231.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Mar 4 20:31:34 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011232.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 4 20:33:35 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011233.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Mar 4 20:35:35 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011234.html

1 0

decisions of the Zope Framework Steering Group
by Martijn Faassen 04 Mar '09

04 Mar '09

Hi there, This document contains the decisions made by the Zope Framework Steering Group: http://svn.zope.org/zopeframework/trunk/decisions.txt This is the project area for the zopeframework steering group: http://svn.zope.org/zopeframework/trunk It is currently designated to contain documents, no code. Regards, Martijn

1 0

Re: [Zope-dev] [Checkins] SVN: zope.component/branches/tseaver-wo_zope_deferred/ Branch removing zope.deferred.
by Tres Seaver 04 Mar '09

04 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Korostelev wrote: > 2009/3/4 Tres Seaver <tseaver(a)palladion.com>: >> Log message for revision 97465: >> Branch removing zope.deferred. >> >> >> Changed: >> D zope.component/branches/tseaver-wo_zope_deferred/src/zope/component/bbb/ > >> -# BBB: Backward-compatibility; 12/05/2004 >> -from bbb.interfaces import * > > Note, that the context-dependent/presentation/view stuff that was in > BBB interfaces are still used in some places, like zope.publisher, so > this needs more careful (re)moving. I think that one of the nice > places for those interfaces is zope.browser, however they are not > necessary browser-related, so maybe they should be moved elsewhere or > just placed in zope.component.interfaces for now, as they're really > tiny. Yup. That was probably a case of premature deprecation (back in 2004). Note that I'm not actually proposing that we merge this branch any time soon: it is a bit of a straw man for the ongoing process conversation. 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJra+4+gerLs4ltQ4RAtw3AJ9sS97lAUFp09XHeYUy9HGgt+DHzQCcDKEY s40FAqfVUgblyg4OosNm7WM= =EyRo -----END PGP SIGNATURE-----

3 6

Declaration of the foundation of the Zope Framework and Steering Group
by Martijn Faassen 04 Mar '09

04 Mar '09

Hi there, Enough discussion. I'm taking a few next steps so we can make progress. I'm going to arbitrarily assume we have enough of a consensus to move forward. Next step is to Just Do It, as Gary said. So, as of right now, we have the Zope Framework. We have a Zope Framework Steering Group. The membership of the Steering Group is Just Me to start with. I'm going to let 4 other people into the group and I'm going to risk offending people by excluding whoever I like. I'm of course going to do my best to work with everybody, in the Steering Group or not; we're just here to help keep things moving in a good set of directions. Who wants to join the Steering Group? Feel free to mail me in private. The Zope Framework is all the zope.* libraries, including all the zope.app.* libraries. That's way too big, it's ridiculous actually, and the priority of the steering group is to get that list down to size as soon as possible. Expect new smaller lists, and expect them to keep shrinking. The first project of the steering group is this: the Zope Framework shouldn't contain a trace of the ZMI. We're going to pull out anything that appears useful out of existing libraries and evict the ZMI out of the Zope Framework, one way or another. Please help, as the success of this project depends on you, Zope Hacker! If you want to make some change to the Zope Framework, start a thread on zope-dev about it. The Steering Group is watching. The Steering Group is going to make decisions in the following way: * a steering group member participates in discussions as normally, saying +1 or -1 or whatever alternative suggestions they may have. * if it's clear there's a consensus by the steering group, we will record the decision in a document in SVN to be announced. If not all steering group members voted and it's "enough time" later, fine, the decision is made by those who did care to contribute. * if there is no consensus by the steering group, the most votes by steering group members in the thread win. It is the task of the steering group to detect this and record it (or delegate its recording by someone else, even better). * if for some reason it's hard to count votes and get consensus in the Steering Group, people can point this out. "Steering Group help, no consensus detected!". We will then reach a consensus. * If there's still no consensus, I'm going to flip a coin and that's going to be the answer. I'm going to do my best to avoid having to flip any coins, as it's very silly to decide on the flip of a coin. * If no steering group member participates in a discussion and consensus is reached, please proceed. Everything's fine. You only need to worry about the steering group if they're actually participating in a discussion or if you don't like the consensus or if no consensus is reached. Feel free to call in the Steering Group and it will fly in. It's not a bird, it's not a plane, it's the Steering Group! The Steering Group has no say over Zope 3, Grok, Zope 2 or whatever. Well, I do have some say over Grok, so currently the steering group is heavily biased towards what Grok wants. :) Regards, Martijn

1 0

Re: [Zope-dev] SVN: zope.component/branches/tseaver-wo_zope_deferred/
by Tres Seaver 04 Mar '09

04 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tres Seaver wrote: > Log message for revision 97465: > Branch removing zope.deferred. This checkin is the branch I had in mind when sketching out a non-CPython-only zope.component story today. Notes on the changes: - - The branch kills off both the use of 'zope.deferredimport' and the 'bbb' subpackage, leaving something which could be used in Jython, or IronPython, or the GAE. - - Ripping out 'zope.deferredimport' required shifting to "from imports" to avoid cycles. I moved one other cycle down into a non-module-scope import, as well, using a 'global base' to avoid extra imports. - - All its tests pass in a buildout. - - Due to the 'test' extra, buildout pulls in a bunch of extra dependencies, which I would like to zap (ZODB? really? just to verify that the persistent registry survives 'dumps' and 'loads'?) - - The branch can be installed into a virtualenv via 'setup.py develop', with only 'zope.interface' and 'zope.event' added. - - 'setup.py test' needs 'zope.testing', but then doesn't do anything (missing metadata). If I added the metadata, the tests would then pull in those extra packages: maybe I'll work on trimming them down, too. - - It probably breaks something in the 'compattests' realm; I haven't tried that, yet. 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJra8y+gerLs4ltQ4RAnxvAJ9WijLQGtxOnqMX1XvNJFS4LWZ+PACfWhqJ KMrDhDwlA+kHYMOVuP34K6k= =K8ZI -----END PGP SIGNATURE-----

5 6

Re: [Zope-dev] Zope2 trunk: getting 'mkzopeinstance' / 'mkzeoinstance' working
by Tres Seaver 04 Mar '09

04 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Andreas Jung wrote: >> I haven't seen an issue with this. What is the exact failure? >> >> Andreas >> >> On Mon, Feb 23, 2009 at 17:46, Tres Seaver <tseaver(a)palladion.com> wrote: >> The scripts run, but produce instances which don't work, because they >> plug in the "base" python, rather than the "zopepy" one. Is anybody >> working on fixing this issue? > > Creating an instance from the SVN checkout itself doesn't work for me > either for the same reason. The created scripts try to use the general > Python interpreter without the correct sys.path and end up missing out > all the dependencies. Right: if you hack it to use the 'zopepy' script, rather than sys.executable, then the instance scripts work. > So far only creating an instance from a source distribution built from > the SVN checkout works for me. - -- =================================================================== 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJotYZ+gerLs4ltQ4RArhKAJ9NbZ6GfApTxw3NzG9/tez5OLrAGQCgynKK REUivQU9PkOHseeIquG7AL0= =zJxt -----END PGP SIGNATURE-----

3 6

Coding style clarifications
by Christian Theune 04 Mar '09

04 Mar '09

Hi, while gathering, cleaning and consolidating the various statements that float around about the coding style for Zope 3, I found a couple of issues that I'd like to get clarification for. What I found is currently gathered at http://svn.zope.org/zope3docs/source/codingstyle/python-style.rst?rev=96729… Which attribute naming is current? ================================== Do we use under_scores or mixedCaseNames? I think I remember that we decided to follow PEP 8 for new code and invoke the "local consistentency" rule on old code. Is that correct? Global variable names ===================== I don't understand that rule. I kept it around because someone might be able to explain it more in-depth and whether it still applies. Import ordering =============== Jim proposed an alternative rule for ordering imports. Is this official? (My vote is +1 on it) Cheers, Christian -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

14 35

Re: [Zope-dev] Review of zc.dict tlotze-blist branch
by Gary Poster 04 Mar '09

04 Mar '09

On Mar 4, 2009, at 2:20 AM, Thomas Lotze wrote: > Gary Poster <gary.poster(a)gmail.com> schrieb: > >>> Index: src/zc/dict/configure.zcml >>> =================================================================== >>> --- src/zc/dict/configure.zcml (.../trunk) (revision 0) >>> +++ src/zc/dict/configure.zcml (.../branches/tlotze-blist) >> (revision 97211) >>> @@ -0,0 +1,5 @@ >>> +<configure xmlns="http://namespaces.zope.org/zope"> >>> + >>> + <include package=".generations" /> >>> + >>> +</configure> >> >> configure.zcml has a semantic of "always include." Because the >> generations code may not work for many people (as we've discussed >> before, and see comment in evolve test below), I'd prefer that the >> generations code have a semantic of "optionally include." Therefore, >> I suggest you rename this to "generations.zcml" or something like >> that. > > Wouldn't it be simpler to just remove this file as it does nothing but > include the configure.zcml of a sub-package? Using the generations > configuration would then read <include > package="zc.dict.generations" /> > instead of <include package="zc.dict" file="generations.zcml" /> which > wouldn't be for the worse either IMO. +1, good idea >> Also as mentioned before on the Zope list, until this API is >> deprecated in favor of one that encourages more granular changes, the >> change to blist only really helps the story for adding new items to >> an >> ordered dict. >> >> The Plone IExplicitOrdering interface looks reasonable, and could >> really take advantage of the blist characteristics. > > I do have that on my to-do list. Do you think we should add some > comment > about this to the code? I think the current performance characteristics are important to note somewhere, at least. Even CHANGES would be sufficient. Thanks, Gary

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 04 Mar '09

04 Mar '09

Summary of messages to the zope-tests list. Period Tue Mar 3 12:00:00 2009 UTC to Wed Mar 4 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: Tue Mar 3 20:21:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011223.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 3 20:23:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011224.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 3 20:25:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011225.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Mar 3 20:27:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011226.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 3 20:29:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011227.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Mar 3 20:31:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011228.html

1 0