- Zope-Dev - Zope lists

zope.app.container 3.5.4 bugfix release
by Christophe Combelles 17 Jul '08

17 Jul '08

I've added a tag for the 3.5.4 bugfix release of zope.app.container. Could someone please add me on the owners list on pypi so that I can upload it? thanks, Christophe

2 4

how do you run the zc.buildout test suite?
by Chris McDonough 17 Jul '08

17 Jul '08

How is zc.buildout meant to have its tests run? On Mac OS X, in a checkout from svn+ssh://svn.zope.org/repos/main/zc.buildout/trunk Doing: $ python2.4 bootstrap/bootstrap.py $ bin/buildout results in: [chrism@vitaminf-2 zc.buildout]$ bin/buildout Develop: '/Users/chrism/projects/zc.buildout/zc.recipe.egg_' Develop: '/Users/chrism/projects/zc.buildout/.' While: Installing. Getting section test2.3. Initializing part test2.3. Getting section python2.3. Error: The referenced section, 'python2.3', was not defined. And doing: $ python2.4 setup.py test -q gives me a raft of test failures, which leads me to believe the tests weren't meant to be run this way. What's the right way to run the test suite? - C

2 1

Buildout site
by Baiju M 17 Jul '08

17 Jul '08

Hi all, Few weeks back Buildout site become live, Jens Vagelpohl setup the site at http://buildout.zope.org/ But I couldn't work further on the site. If anyone want contribute to the content please add it here: svn co svn://svn.zope.org/repos/main/buildout-website/trunk/ Regards, Baiju M

3 3

transaction.doom() and ZPublisher
by Paul Winkler 17 Jul '08

17 Jul '08

Hi, I noticed that Zope 2.11 includes a recent version of the transaction module including the transaction.doom() method. But I don't see any check for it in ZPublisher. So, if any code calls transaction.doom(), the publisher will raise a user-visible exception when it tries to call commit(). This seems less than useful :-) In the discussion I've seen of this method, eg. https://bugs.launchpad.net/zope3/+bug/98382 and http://markmail.org/message/3yshpmltvhevnrff it sounds like other people share my expectation... namely, that the developer should not have to do anything special after calling transaction.doom(); the transaction is not committed, and the user won't see an exception. Is that the concensus? If so, there's an easy solution - apply something like the attached patch. Anybody disagree? -- Paul Winkler http://www.slinkp.com

4 6

Zope Tests: 5 OK
by Zope Tests Summarizer 17 Jul '08

17 Jul '08

Summary of messages to the zope-tests list. Period Wed Jul 16 11:00:00 2008 UTC to Thu Jul 17 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Jul 16 20:57:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009865.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 16 20:58:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009866.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 16 21:00:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009867.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 16 21:01:54 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009868.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 16 21:03:24 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009869.html

1 0

Re: [Repoze-dev] Z2.9 incompatibilites with tarballs on dist.repoze.org
by Chris McDonough 16 Jul '08

16 Jul '08

Chris McDonough wrote: > Alan Milligan wrote: >> Hi, >> >> I'm in the midst of rolling repoze out on our BastionLinux RPM's (at >> https://linux.last-bastion.net/LBN/up2date/plope/6 (repoze.* and zope.*) >> for *exactly* what files and versions are being shipped). >> >> We're at zope-2.9.9, the latest release that runs up plone-2.5.x. I've >> thus packaged up the required components on >> http://dist.repoze.org/zope2/2.9/ >> >> However, the zope.interface-3.4.0 is from a later version of Z3 than >> ships with Z2 (I think this is still at 3.3) and when zope.app.component >> from the Z2 tree is invoked through paster, it dies horribly when it >> can't find zope.interface.adapter.Surrogate - which appears to have >> vanished between releases. Downgrading to zope.interface-3.3.0, as >> shipped with zope-2.9.9 fixes this (insofar as zope2.wsgi now runs up >> from the command line). > > Eek. You're right. I mispackaged. The zope.interface version up there now is > the 3.2 version that ships with Zope 2.9. We maintain multiple indexes, and we > haven't yet automated a buildbot to test them so it's exceedingly difficult to > make sure they all work at all times. Apologies. > >> Similarly, the ZODB3 version (3.7.2) is later than that shipped in >> zope-2.9.9. I don't expect any issues with this (yet at least) as I'm >> running vanilla zeo from zope-2.9.9 > > That doesn't cause any problem in our testing. > >> Is this anomaly simply due to hoping that nobody will notice if the >> Z2.10 tarballs are foisted on Z2.9 users - or indeed are these genuinely >> required, and I'm about to enter module import hell? > > No, I think you should be good now with the new distribution. Thanks for the > notification. > >> Note that the zope.proxy and zope.testing tarballs are similarly >> incorrect, but they too appear benign. > > I also believe these are benign. > > I'm currently running an easy_install to make sure. Well it *would* have worked if easy_install didn't go off to download.zope.org to find the latest zope.interface package due to a promiscuous distribution_links in the ZODB package. See also http://plope.com/Members/chrism/distribution_links_considered_harmful .. Ugh. I'll need to re-roll that ZODB egg without the dependency-links and put it up there. I'll post when that's done. - C _______________________________________________ Repoze-dev mailing list Repoze-dev(a)lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev

1 0

Re: [Checkins] SVN: zope.i18n/branches/regebro-pluralsupport/src/zope/i18n/ Changed the API. It's unwieldy as it is, so better have separate methods
by Lennart Regebro 16 Jul '08

16 Jul '08

On Wed, Jul 16, 2008 at 20:22, Stephan Richter <srichter(a)cosmos.phy.tufts.edu> wrote: > On Wednesday 16 July 2008, Lennart Regebro wrote: >> Log message for revision 88417: >> Changed the API. It's unwieldy as it is, so better have separate method >> for plurals. > > It looks to me as if you only support one singular and one plural form. Nope. Although I currently only test that case. > I have read some commentary a long time ago, that some languages, like Polish, have > multiple plural forms. Is that supported? Should be, but it's not tested yet. While talking about this, what would a ZPT implementation of this best look like? An i18n:count statement that takes expressions? <p i18n:translate="" i18n:count="view/file_count">There are %d files</p> Or? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64

3 6

Re: [Zope-dev] Tesing a module against against dependencies in different versions
by Fred Drake 16 Jul '08

16 Jul '08

On Wed, Jul 16, 2008 at 2:59 PM, Andreas Jung <lists(a)zopyx.com> wrote: > we maintain some modules that should work against different versions of > dependent module. E.g. my z3c.sqlalchemy module should work with > > Sqlalchemy 0.3.X and zope.interface 3.0.X > or > SQLAlchemy >=0.4.X and zope.interface>=3.3.0 > > The codebase right works with both combinations. I am not sure how test such > configurations automatically because the dependent modules and their > versions are fixed within the setup.py. Is there some way together with > Buildout, zope.testing & friends? This remains a tricky case. :-( I suspect the best thing is for the setup.py not to mention any of the packages for which there are different names, and the versions should be specified in the buildout.cfg as requirements for separate test scripts. I.e., zope.interface could be mentioned in setup.py (sans version), but the sql alchemy packages would not be since the names differ. You could then create test scripts like so: [test-one] recipe = zc.recipe.testrunner eggs = z3c.sqlalchemy Sqlalchemy >=0.3.0, <0.4.0 zope.interface >=3.0.0 [test-two] recipe = zc.recipe.testrunner eggs = z3c.sqlalchemy SQLAlchemy >=0.4.0 zope.interface >=3.3.0 I expect you could come up with better names than test-one and test-two; I'm creativity-challenged at the moment. :-) -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller

1 0

Tesing a module against against dependencies in different versions
by Andreas Jung 16 Jul '08

16 Jul '08

Hi there, we maintain some modules that should work against different versions of dependent module. E.g. my z3c.sqlalchemy module should work with Sqlalchemy 0.3.X and zope.interface 3.0.X or SQLAlchemy >=0.4.X and zope.interface>=3.3.0 The codebase right works with both combinations. I am not sure how test such configurations automatically because the dependent modules and their versions are fixed within the setup.py. Is there some way together with Buildout, zope.testing & friends? Andreas -

1 0

Re: [Checkins] SVN: zope.app.locales/trunk/ added filePattern parameter for tal_strings to be able to not only parse
by Benji York 16 Jul '08

16 Jul '08

On Wed, Jul 16, 2008 at 10:41 AM, Juergen Kartnaller <juergen(a)kartnaller.at> wrote: > Log message for revision 88402: > added filePattern parameter for tal_strings to be able to not only parse > "*.pt" files. This looks like a new feature, and as such warrants a version bump to 3.5.0. > Changed: > U zope.app.locales/trunk/CHANGES.txt > U zope.app.locales/trunk/setup.py > U zope.app.locales/trunk/src/zope/app/locales/extract.py > > -=- > Modified: zope.app.locales/trunk/CHANGES.txt > =================================================================== > --- zope.app.locales/trunk/CHANGES.txt 2008-07-16 13:35:48 UTC (rev 88401) > +++ zope.app.locales/trunk/CHANGES.txt 2008-07-16 14:40:57 UTC (rev 88402) > @@ -2,9 +2,11 @@ > CHANGES > ======= > > -3.4.5 (unreleased) > +3.4.5 (2008-07-16) > ------------------ > > +* added filePattern parameter for tal_strings to be able to not only parse > + "*.pt" files. > * Updated Dutch translation > > 3.4.4 (2008-03-05) > > Modified: zope.app.locales/trunk/setup.py > =================================================================== > --- zope.app.locales/trunk/setup.py 2008-07-16 13:35:48 UTC (rev 88401) > +++ zope.app.locales/trunk/setup.py 2008-07-16 14:40:57 UTC (rev 88402) > @@ -22,7 +22,7 @@ > return open(os.path.join(os.path.dirname(__file__), *rnames)).read() > > setup(name='zope.app.locales', > - version = '3.4.5dev', > + version = '3.4.5', > author='Zope Corporation and Contributors', > author_email='zope3-dev(a)zope.org', > description='Zope locale extraction and management utilities', > > Modified: zope.app.locales/trunk/src/zope/app/locales/extract.py > =================================================================== > --- zope.app.locales/trunk/src/zope/app/locales/extract.py 2008-07-16 13:35:48 UTC (rev 88401) > +++ zope.app.locales/trunk/src/zope/app/locales/extract.py 2008-07-16 14:40:57 UTC (rev 88402) > @@ -441,7 +441,11 @@ > context = config(site_zcml, features=("devmode",), execute=False) > return context.i18n_strings.get(domain, {}) > > -def tal_strings(dir, domain="zope", include_default_domain=False, exclude=()): > +def tal_strings(dir, > + domain="zope", > + include_default_domain=False, > + exclude=(), > + filePattern='*.pt'): > """Retrieve all TAL messages from `dir` that are in the `domain`. > > >>> from zope.app.locales import extract > @@ -480,6 +484,16 @@ > >>> extract.tal_strings(dir, domain='xml') > {u'Link Content': [('...xml.pt', 8)]} > > + We also provide a file with a different file ending: > + > + >>> testpt = open(os.path.join(dir, 'test.html'), 'w') > + >>> testpt.write('<tal:block i18n:domain="html" i18n:translate="">html</tal:block>') > + >>> testpt.close() > + > + >>> extract.tal_strings(dir, domain='html', include_default_domain=True, > + ... filePattern='*.html') > + {'html': [('...test.html', 1)]} > + > Cleanup > > >>> import shutil > @@ -497,7 +511,7 @@ > def write(self, s): > pass > > - for filename in find_files(dir, '*.pt', exclude=tuple(exclude)): > + for filename in find_files(dir, filePattern, exclude=tuple(exclude)): > f = file(filename,'rb') > start = f.read(6) > f.close() > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins >

1 0