- Zope-Dev - Zope lists

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Andreas Jung 12 May '09

12 May '09

On 12.05.09 16:02, Andreas Jung wrote: > On 12.05.09 15:25, Chris Withers wrote: > >> Andreas Jung wrote: >> >>>> - It's being done into the beta phase of Zope 2.12 >>>> >>> changes in this *early* beta phase, no changes after beta 2 are >>> acceptable). >>> >> This feels like an abuse of your position as release manager. >> > I call it adjusting the policies as needed for getting things done and > for getting important things and I emphasize once again: it happend > during beta 1 - we proceeded always this way to some degree. I am not > the slave to the policy. > > >> Can you honestly tell me that if it was anyone other than you, you'd >> let them merge these changes after you'd already cut beta 1? >> >> >>> Feature 2 (the one you are complaining about): Making <environment> a >>> multisection. >>> >>> The rational behind this change is clear: making the Zope configuration >>> more modular for bigger setups. In complex setups there is a need for >>> having this >>> extension if you don't want and can't to build a monolithic >>> configuration. >>> >> There are plenty of options other than this, the one that jumps to >> mind would be a buildout recipe similar to collective.recipe.template >> that staples together your various config file snippets into one >> zope.conf. >> > Possibly. As said, I am not married with this particular feature. > >> >>> "The community" working on Zope 2.12 was basically Hanno doing most of >>> the work, >>> Tres and me. >>> >> That's not quite true, other people have been contributing fixes and I >> know I spent a lot of time getting Zope 2.12 to work in a buildout >> without the need for rewriting the zope2instance recipe. >> >> But, that aside, people working on Zope 2.12 does not make up the >> whole community, there's the whole userbase, or even potential >> userbase to consider. >> > We try our best for not breaking things - this happens from time to time > - usually > unintended. It's perfectly fine when an incompatiblity pops up during > the beta phase. > No need for crying out lould. > > >>> So the actual development is driven by the people doing the >>> work and by >>> their needs. >>> >> I agree with this. >> >> >>> Not every new feature must be discussed in depth on the list. >>> >> I don't agree with this. New features should always be discussed. Had >> you posted the messages you posted to the bug tracker to this list >> instead, and then waited a week or so for people to comment, that >> would have been fine. >> > A mis-configuration/mis-feature of Launchpad. There should be a list for > all LP > related traffic. Right now you have to be member of the Zope 2 group on LP. > Something we can easily fix. > > >> >>> Consider this being a defect of your release process and planning. >>> >> *My* release process and planning? >> > Sorry, basically not my problem - if you depend on bleeding-edge > releases, you > have to be aware of the consequences. And since we have no schedule for > the release, your planning is pretty much obsolete. > > >> >> >>> The primary purpose of the <environment> section is for making >>> additional environment >>> variables available with Zope. I consider being an "internal" >>> functionality. >>> >> Well, I consider it less than internal ;-) >> > That <http://dict.leo.org/ende?lp=ende&p=thMx..&search=That>'s > <http://dict.leo.org/ende?lp=ende&p=thMx..&search=s> a > <http://dict.leo.org/ende?lp=ende&p=thMx..&search=a> matter > <http://dict.leo.org/ende?lp=ende&p=thMx..&search=matter> of > <http://dict.leo.org/ende?lp=ende&p=thMx..&search=of> opinion > <http://dict.leo.org/ende?lp=ende&p=thMx..&search=opinion>. > >> >>>> Andreas, please revert this change until people have had a chance to >>>> look at it properly. >>>> >>> Reverting the change without a discussion was offending (see above). And >>> I want to emphasize >>> once more: none of the people doing the development work need to ask for >>> every single >>> change made to the Zope 2 core for public feedback. >>> >> I actually agree with this, but I don't agree in the case of new >> features or in the case of backwards compatibility breakages. >> > See above. I could not commit the fixes and new features earlier because > of constraints that don't belong into public. > >> Nevertheless, if you're intent on bulldozing this change through, >> please consider using and writing a test for the one additional like I >> gave you that should result in getConfiguration().environment being >> the single dict it always has been and should logically be. >> > Where is the test telling us that getConfiguration().environment has to > be a dict (as it is used > only internally)? > > Andreas > > -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

2 1

[buildbot] zc.buildout (small) failures
by Sebastien Douche 12 May '09

12 May '09

http://misc.buildbot.securactive.org/builders/zc.buildout-py2.4-32bit-linux… http://misc.buildbot.securactive.org/builders/zc.buildout-py2.4-64bit-linux… http://misc.buildbot.securactive.org/builders/zc.buildout-py2.6-32bit-linux… http://misc.buildbot.securactive.org/builders/zc.buildout-py2.6-64bit-linux… Failed example: print 'X'; print system( zc.buildout.easy_install._safe_arg(sys.executable)+' '+ 'bootstrap.py --version 1.1.1'); print 'X' Expected: X Generated script '/sample/bin/buildout'. <BLANKLINE> X Got: X Generated script '/sample/bin/buildout'. /tmp/tmp64BRh4/zc.buildout-1.1.1-py2.6.egg/zc/buildout/buildout.py:21: DeprecationWarning: the md5 module is deprecated; use hashlib instead import md5 <BLANKLINE> X --------------------------------------------------------------------------------------------- Expected: X No local packages or download links found for zc.buildout==UNKNOWN error: Could not find suitable distribution for Requirement.parse('zc.buildout==UNKNOWN') Traceback (most recent call last): File "bootstrap.py", line 78, in <module> ) == 0 AssertionError <BLANKLINE> X Got: X No local packages or download links found for zc.buildout==UNKNOWN error: Could not find suitable distribution for Requirement.parse('zc.buildout==UNKNOWN') Traceback (most recent call last): File "bootstrap.py", line 75, in ? PYTHONPATH= AssertionError <BLANKLINE> X Cheers -- Sebastien Douche <sdouche(a)gmail.com>

3 3

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Andreas Jung 12 May '09

12 May '09

On 12.05.09 16:53, Andreas Jung wrote: > >> That said, I think the process issues are more important than sepcific >> changes here: >> >> - We are too late in the cycle to be jamming in huge piles of features. >> > Two is not a big pile. We had changes other than bugfixes after beta at > least in Zope 2.9, 2.10 and you added yourself a feature after 2.12.0b1. > So let's be pragmatic, not dogmatic. > >> - ChrisW is correct that adding issues to Launchpad does *not* >> constitute sufficient notice of such features. Probably less than >> ten percent of the "core" developers actually get Launchpad e-mails. >> > Every active core developer should be member of Zope 2 dev team: > > https://launchpad.net/~zope2-dev > > It is up to each developer to join the team - this is not much different > from > a mailinglist membership. > > Andreas > > -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

1 0

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Andreas Jung 12 May '09

12 May '09

On 12.05.09 16:37, Andreas Jung wrote: > On 12.05.09 15:29, Sidnei da Silva wrote: > >> On Tue, May 12, 2009 at 10:25 AM, Chris Withers <chris(a)simplistix.co.uk> wrote: >> >> >>> The problem is that the visibility of issues in Launchpad is very poor. >>> You can't even get notifications of bugs unless you're part of the >>> development team. Using it for features means that no-one in the wider >>> community is likely to even know what's going on. That's bad as it means >>> that no-one gets the opportunity to make suggestions or comments. This >>> could be improved by getting issue emails sent to this list too, is that >>> possible? >>> >>> >> Yes, that is possible. But I fear this list might not be the most >> appropriate place. Maybe we should revive the 'zope-collector' mailing >> list (or am I dreaming that such a list ever existed?) >> >> > I *think* there was such a list. LP provides mailinglist support for > for each group > > https://launchpad.net/~zope2-dev > > but I see no option for using such a list for tracker notifications. > > I suggest to add a pseudo member to the Zope 2 dev team and configure its > mail address to some new mailman list on lists.zope.org where ppl > can subscribe/unsubscribe at their own joy and pleasure. > > If there are no other options, please vote on my proposal. > > Andreas > > > > -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

1 0

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Sidnei da Silva 12 May '09

12 May '09

On Tue, May 12, 2009 at 11:37 AM, Andreas Jung <andreas(a)andreas-jung.com> wrote: > I *think* there was such a list. LP provides mailinglist support for > for each group > > https://launchpad.net/~zope2-dev That's an option, creating a mailing list for the team. However it's not required. See below. > but I see no option for using such a list for tracker notifications. > > I suggest to add a pseudo member to the Zope 2 dev team and configure its > mail address to some new mailman list on lists.zope.org That's not needed. Since the zope2-dev team is automatically subscribed to issues, we only need to set it's contact address. If we set that address to zope-dev(a)lists.zope.org, then issues will automatically be delivered to it. -- Sidnei da Silva Canonical Ltd. Landscape · Changing the way you manage your systems http://landscape.canonical.com

1 0

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Chris Withers 12 May '09

12 May '09

Andreas Jung wrote: > but I see no option for using such a list for tracker notifications. > > I suggest to add a pseudo member to the Zope 2 dev team and configure its > mail address to some new mailman list on lists.zope.org where ppl > can subscribe/unsubscribe at their own joy and pleasure. > > If there are no other options, please vote on my proposal. +10 for getting the mail just to come to zope-dev, where more people will see it. +1 for kicking the old zope-collector list back into action. Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

Publishing our company internal Zope extensions and fixes
by Andreas Jung 12 May '09

12 May '09

Hi there, we are currently combing through our company internal Zope (2.11) version and trying to identify the stuff that is of interest for the public and the Zope 2 core (including some ZODB extensions/changes). I will create a ticket on Launchpad (containing a detailed description + patch) for the interesting items (we have roughly 50 of them) over the next days. All items are prefixed with "[DM]". Everyone is invited to look at the stuff and comment on it. I also reserve the right merging some of the changes into the current trunk until the next Zope 2.12 beta2 release (intentionally breaking the rule that no new features should be added within the beta phase). Andreas

3 5

Zope Tests: 8 OK
by Zope Tests Summarizer 12 May '09

12 May '09

Summary of messages to the zope-tests list. Period Mon May 11 12:00:00 2009 UTC to Tue May 12 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 11 20:52:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011683.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon May 11 20:54:31 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011684.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon May 11 20:56:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011685.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon May 11 20:58:35 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011686.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon May 11 21:00:41 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011687.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon May 11 21:02:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011688.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon May 11 21:04:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011689.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon May 11 21:07:03 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011690.html

1 0

Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ merged haufe-legacy-integration branch
by Chris Withers 12 May '09

12 May '09

Hi All, I have some real issues with this work being done in the fashion it has: - It's being done into the beta phase of Zope 2.12 - There's been zero discussion with the community before this was done. Have I missed something here? In particular: > Modified: Zope/trunk/src/ZPublisher/Publish.py > +from zope.event import notify > > +from pubevents import PubStart, PubSuccess, PubFailure, \ > + PubBeforeCommit, PubAfterTraversal > + Has anyone looked at the performance implications of all these events (which most of us will never use) being fired off? > except: > + # save in order to give 'PubFailure' the original exception info > + exc_info = sys.exc_info() As this is never deleted, does it not leak stack frames? > Modified: Zope/trunk/src/Zope2/Startup/handlers.py > =================================================================== > --- Zope/trunk/src/Zope2/Startup/handlers.py 2009-05-12 08:32:23 UTC (rev 99865) > +++ Zope/trunk/src/Zope2/Startup/handlers.py 2009-05-12 08:49:29 UTC (rev 99866) > @@ -184,8 +184,10 @@ > """ > > # Set environment variables > - for k,v in config.environment.items(): > - os.environ[k] = v > + d = {} > + for s in config.environment: > + d.update(s) > + os.environ.update(d) The change in the config that makes this necessary is pretty unacceptable. I have lots of code that looks in config.environment, now I have to find all that code and change it in a similar fashion. WTF? > - <section type="environment" attribute="environment" name="*"> > + <multisection type="environment" attribute="environment" name="*"> > <description> > A section which allows a user to define arbitrary key-value pairs for > use as environment variables during Zope's run cycle. It > is not recommended to set system-related environment variables such as > PYTHONPATH within this section. > </description> > - </section> > + </multisection> ...this is the offending change. Andreas, please revert this change until people have had a chance to look at it properly. Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 11 May '09

11 May '09

Summary of messages to the zope-tests list. Period Sun May 10 12:00:00 2009 UTC to Mon May 11 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 10 20:55:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011675.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun May 10 20:57:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011676.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun May 10 20:59:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011677.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun May 10 21:01:10 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011678.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sun May 10 21:03:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011679.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun May 10 21:05:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011680.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun May 10 21:07:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011681.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sun May 10 21:09:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011682.html

1 0