Re: [Zope-dev] RFC: 3.4.1 KGS?
Hello Marius, Wednesday, March 31, 2010, 2:50:33 PM, you wrote: ... MG> * look at other possible bugfix upgrades, see if there are any MG>important bugs fixed (zope.release's bin/list-latest is useful here) ... I created a sheet with versions http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQ&output=html Right now it's a sort of highest version affordable after a quick scan through the version. I'm thinking about doing one more round to take a closer look and probably screw some versions back. -- Best regards, Adam GROSZERmailto:agros...@gmail.com -- Quote of the day: We die only once, and for such a long time. - Moliere ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [ann] BugDay 2010-04-24
Hello, As discussed at the weekly meeting, we're planning a BugDay. The wiki page is here: http://wiki.zope.org/bluebream/BugDaysList Don't wonder, we're planning it together with BB. Feel free to add your inputs. -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: It is generally agreed that "Hello" is an appropriate greeting because if you entered a room and said "Goodbye," it could confuse a lot of people. - Dolph Sharp ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] "Comply with repository policy" ?
Hi! Tres Seaver wrote: > o Run the automated fixups:: > > $ /path/to/zrp/bin/zope-org-fix-project . > ... ... Just in case *someone* cares: zope-org-fix-project was written for copyright headers with a specific layout. Depending on the actual layout it removes the sentence "All Rights Reserved." partially or completely. So depending on a layout difference (line break or not) it produces copyright headers with different content. Doesn't make any sense to me, but the people I already asked don't care. Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] "Comply with repository policy" ?
On 04/09/2010 12:36 PM, yuppie wrote: > Hi! > > > Tres Seaver wrote: >> o Run the automated fixups:: >> >>$ /path/to/zrp/bin/zope-org-fix-project . >>... ... > > Just in case *someone* cares: > > zope-org-fix-project was written for copyright headers with a specific > layout. Depending on the actual layout it removes the sentence "All > Rights Reserved." partially or completely. > > So depending on a layout difference (line break or not) it produces > copyright headers with different content. > > Doesn't make any sense to me, but the people I already asked don't care. Humm. You asked me privately but I haven't found time to respond yet. :) Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [ann] BugDay 2010-04-24
On 04/09/2010 12:24 PM, Adam GROSZER wrote: > Hello, > > As discussed at the weekly meeting, we're planning a BugDay. Cool. Somewhat sad it's a Saturday, but I'll make it somehow. :) Christian -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Thu Apr 8 12:00:00 2010 UTC to Fri Apr 9 12:00:00 2010 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: Thu Apr 8 21:29:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013884.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 8 21:31:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013885.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:33:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013886.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:35:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013887.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:37:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013888.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:39:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013889.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] "Comply with repository policy" ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: > Hi! > > > Tres Seaver wrote: >> o Run the automated fixups:: >> >> $ /path/to/zrp/bin/zope-org-fix-project . >> ... ... > > Just in case *someone* cares: > > zope-org-fix-project was written for copyright headers with a specific > layout. Depending on the actual layout it removes the sentence "All > Rights Reserved." partially or completely. > > So depending on a layout difference (line break or not) it produces > copyright headers with different content. > > Doesn't make any sense to me, but the people I already asked don't care. The "All Rights Reserved" is a little senseless, since the following language turns around and says that the files are covered by the ZPL. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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 iEYEARECAAYFAku/LvYACgkQ+gerLs4ltQ7ecQCdEuEfp+0QRVjLBbmP+O3afM8r 31kAoJrM6SRtlxkew59Cx33jSN+Ip87D =jJ1M -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] env var support for zc.buildout
On Thu, Apr 8, 2010 at 9:32 AM, Florian Friesdorf wrote:
> On Thu, Apr 08, 2010 at 02:24:53PM +0200, Christian Theune wrote:
>> Hi,
>>
>> On 04/08/2010 12:59 PM, Florian Friesdorf wrote:
>> > On Thu, Apr 08, 2010 at 08:56:18AM +0200, Christian Theune wrote:
>> >> On 04/08/2010 04:27 AM, Florian Friesdorf wrote:
>> >>> environment variable support for zc.buildout, including extends!
>> >>>
>> >>> https://bugs.launchpad.net/zc.buildout/+bug/557769
>> >>>
>> >>> works for me so far
>>
>> Actually the env recipe was more of a hack to get going and then we
>> forgot to propose getting it into buildout.
>>
>> OTOH handling it as a recipe allows for some other nice tricks, e.g.
>> overriding by extensions.
>>
>> Maybe a specialised part-name, like versions would be helpful so that
>> buildout could pre-populate that part during initialisation and then
>> allow configurations to override individual values.
>
> that would be nice indeed, but again would not work for extends
>
> We currently use it for 5 very similar sites that share one repository
> but use 5 checkouts of it:
>
> base.cfg
> [buildout]
> parts = instance
>
> develop = ...
> eggs = ...
> zcml = ...
>
> [instance]
> ...
>
>
> site-1.cfg
> [buildout]
> eggs +=
> zcml +=
>
>
> testenv.cfg
> [buildout]
> extends =
> base.cfg
> ${env:site}.cfg
>
>
>
>
> deploy.cfg
> [buildout]
> extends =
> base.cfg
> ${env:site}.cfg
>
>
>
>
> % site=site-1 ./bin/buildout -c deploy.cfg
Your extends usage seems a bit convoluted. Why not just have:
- deploy.cfg extend base.cfg
- site1-1.cfg etc extend deploy.cfg
Then you'd just:
% ./bin/buildout -c site-1.cfg
Jim
--
Jim Fulton
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Fri, Apr 9, 2010 at 10:27 AM, Fred Drake wrote: > Setting the ZF as maintainer appears sufficient to appease the policy checker. Or not. The fixer script won't edit this, but the checker script will still whine about it. Changing the author to the ZF really isn't a good thing; if anything, the maintainer (and maintainer_email!) should be set to the ZF (and zope-dev?). Changing the author doesn't really make sense, and is falsification for many packages (certainly for all those created before the ZF existed). -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: > Log message for revision 110702: > correct metadata: I really did write this. > Setting the ZF as maintainer appears sufficient to appease the policy > checker. Hmm, that doesn't work for me: $ svn co $ZSVN/ZConfig/trunk ZConfig $ cd ZConfig $ ../zope.repositorypolicy/bin/zope-org-check-project . setup.py: author not declared as "Zope Foundation and Contributors" \ (found: "Fred L. Drake, Jr.") It seems reasonable to me that it *should* work, though I'm not sure how to write the code which tests that. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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 iEYEARECAAYFAku/PP8ACgkQ+gerLs4ltQ4lFwCgzVbximbdm3lLwLkBTNhI+nzK GjEAnRZQAXCcVPQce8UDI1K59ZZLUodn =Tunh -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Fri, Apr 9, 2010 at 10:43 AM, Tres Seaver wrote: > It seems reasonable to me that it *should* work, though I'm not sure how > to write the code which tests that. See my later follow-up as well. In particular, while it *may* be reasonable to set the ZF as maintainer, it's not clear that it's the right thing either. Why shouldn't some "Grok Team" be listed as the maintainer for the grok packages, with an appropriate email? That seems preferable to me. I think the *right* thing to do is update the copyrights to reflect the copyright ownership, but not to otherwise change package metadata. -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] env var support for zc.buildout
On Fri, Apr 09, 2010 at 10:16:51AM -0400, Jim Fulton wrote:
> > We currently use it for 5 very similar sites that share one repository
> > but use 5 checkouts of it:
> >
> > base.cfg
> > [buildout]
> > parts = instance
> >
> > develop = ...
> > eggs = ...
> > zcml = ...
> >
> > [instance]
> > ...
> >
> >
> > site-1.cfg
> > [buildout]
> > eggs +=
> > zcml +=
> >
> >
> > testenv.cfg
> > [buildout]
> > extends =
> > base.cfg
> > ${env:site}.cfg
> >
> >
> >
> >
> > deploy.cfg
> > [buildout]
> > extends =
> > base.cfg
> > ${env:site}.cfg
> >
> >
> >
> >
> > % site=site-1 ./bin/buildout -c deploy.cfg
>
> Your extends usage seems a bit convoluted. Why not just have:
>
> - deploy.cfg extend base.cfg
>
> - site1-1.cfg etc extend deploy.cfg
>
> Then you'd just:
>
> % ./bin/buildout -c site-1.cfg
That would mean:
- 1 base.cfg
- 1 deploy.cfg
- 1 testenv.cfg
- 5 site-specific extending deploy.cfg
- 5 site-specific extending testenv.cfg
total: 13 files
Site-specific information reside in two cfgs, which is error-prone.
In contrast to our current setup, with env var support, without
the need to duplicate information.
- 1 base.cfg
- 1 deploy.cfg
- 1 testenv.cfg
- 5 site specific cfgs
total: 8 files
Site-specific information could be factored out, as in the setup with
env var support:
testenv-site-1.cfg:
[buildout]
extends =
testenv.cfg
site-1.cfg
Information would not be duplicated but the amount of files increases to
18.
Further we use a dev environment tailored for local individual
development in contrast to the testenv which is meant for the customer
to be kept up-to-date about the development, without e.g. PDBDebugMode.
With that dev environment the numbers are 18 (with site-specific info
in three places) or 23 vs. 9 files.
This idea can be taken further to mass hosting in dedicated instances
but based on one buildout, or branches of one buildout that share the
majority of stuff.
Other use cases coming to my mind:
- ip address for zope to listen on: instead of hard-coded 8080 or
127.0.0.1:8080, you can have ${env:MYPROJECT_LISTEN} and people being
involved in several projects can choose in order to have several
buildouts running in parallel
- location of the Data.fs: I like to have the Data.fs outside of the
buildout dir for development, which enables the use of 'git clean
-xdf', i.e. wiping everything which is not tracked.
I like the idea of the need to configure the name of the environment
section:
[buildout]
environment=env
extends = ${env:...}
At the time the extends are processed, the whole buildout section is
already read into the options dict, so configuration of the name of the
environment section is easily possible and can be used to trigger the
substitution code:
if extends:
envsecname = options.get('environment')
if envsecname:
# do variable substitution like in my patch
# if no environment is specified nothing changes
# continue normally
I would not pop() the options, so the name of the environment section
can be queried by other parts of buildout. Likewise, extends could not
be pop()'ed - both then would need to go onto a list, which buildout
checks, in order not to complain about them being unused.
If I could get commit acces to svn.zope.org, I would further work on
this in a separate branch, more effective than via patches. Committer
agreement I can fax/email. I am not committing to branches that don't
belong to me, without prior consultation. So far I have commit access to
the plone repo, which might be meaningless or at least a minor sign of
credibility.
I hope I could clarify the usefulness of env var support.
florian
--
Florian Friesdorf
GPG FPR: EA5C F2B4 FBBB BA65 3DCD E8ED 82A1 6522 4A1F 4367
Jabber/XMPP: f...@chaoflow.net
OTR FPR: 9E191746 213321FE C896B37D 24B118C0 31785700
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
pgpi3ZxMihuvn.pgp
Description: PGP signature
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] "Comply with repository policy" ?
Hi! Tres Seaver wrote: > yuppie wrote: >> Tres Seaver wrote: >> So depending on a layout difference (line break or not) it produces >> copyright headers with different content. >> >> Doesn't make any sense to me, but the people I already asked don't care. > > The "All Rights Reserved" is a little senseless, since the following > language turns around and says that the files are covered by the ZPL. I'm not opposed to removing that phrase. What I don't like is the fact that it is removed randomly based on a bug in a script that is made for a different purpose. I think a change like that should be based on an official policy change, including new coding style guidelines: http://docs.zope.org/zopetoolkit/codingstyle/python-style.html#license-statement-module-docstring Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Fri, Apr 9, 2010 at 10:57 AM, Fred Drake wrote: > I think the *right* thing to do is update the copyrights to reflect > the copyright ownership, but not to otherwise change package metadata. +1 -- Benji York ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Summary of this weeks' meeting
On 4/8/10 8:30 PM, Jan Smith wrote: > I've published the irc meeting summaries on the Australian OzZope site > - it also has an rss feed available. > http://www.ozzope.org/weekly-zope-development-meeting Could this be added to planetzope.org ? The planet's feed is also announced on #zope. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Apr 9, 2010, at 10:57 AM, Fred Drake wrote: > On Fri, Apr 9, 2010 at 10:43 AM, Tres Seaver wrote: >> It seems reasonable to me that it *should* work, though I'm not sure how to >> write the code which tests that. > > See my later follow-up as well. > > In particular, while it *may* be reasonable to set the ZF as > maintainer, it's not clear that it's the right thing either. Why > shouldn't some "Grok Team" be listed as the maintainer for the grok > packages, with an appropriate email? That seems preferable to me. > > I think the *right* thing to do is update the copyrights to reflect > the copyright ownership, but not to otherwise change package metadata. Why was the check for author even included in the checker/fixer scripts? Can you point us to the Zope Foundation bylaws or a policy document that requires this? I cannot find this in a contributor agreement. Zvezdan ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Stacking zope.component registries
On Thu, Apr 08, 2010 at 10:15:22PM -0400, Stephan Richter wrote:
> On Thursday 08 April 2010, Martin Aspeli wrote:
> > Right. However, any calls to provideAdapter() and friends would still
> > use the global registry, unless I monkey patch
> > zope.component.globalregistry.base, as would any ZCML directives, I guess.
>
> That's not really monkey patching. :-) I would consider this a valid part of
> the API. :-)
Then it's _badly-designed_ API. Look at globalregistry.py from
zope.component 3.4.0:
base = BaseGlobalComponents('base')
from zope.testing.cleanup import addCleanUp
addCleanUp(lambda: base.__init__('base'))
globalSiteManager = base
def getGlobalSiteManager():
return globalSiteManager
def provideAdapter(factory, adapts=None, provides=None, name=''):
base.registerAdapter(factory, adapts, provides, name, event=False)
...
There are two names for the same thing: 'base' and 'globalSiteManager'.
Different methods use different names. There's an assumption that you
can call __init__ on it before and after every test that uses placeless
setup. (I hadn't noticed that last part before; I assume it'll override
base.__bases__ and destroy any attempts of stacking.)
Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
