- Zope-Dev - Zope lists

Zope Tests: 4 OK
by Zope Tests Summarizer 19 Oct '08

19 Oct '08

Summary of messages to the zope-tests list. Period Sat Oct 18 11:00:00 2008 UTC to Sun Oct 19 11:00:00 2008 UTC. There were 4 messages: 4 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Oct 18 20:48:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010334.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 18 20:49:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010335.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 18 20:52:47 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010336.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Oct 18 20:54:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010337.html

1 0

Zope Tests: 4 OK
by Zope Tests Summarizer 18 Oct '08

18 Oct '08

Summary of messages to the zope-tests list. Period Fri Oct 17 11:00:00 2008 UTC to Sat Oct 18 11:00:00 2008 UTC. There were 4 messages: 4 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Oct 17 20:47:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010330.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Oct 17 20:49:14 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010331.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Oct 17 20:52:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010332.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Oct 17 20:53:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010333.html

1 0

traversal: different with and without a request
by Christian Theune 17 Oct '08

17 Oct '08

Hi, we stumbled over an annoyance that took a while to debug: Writing an ITraversable, we used zope.traversing.api.traverse() in a test to verify our code. We registered the ITraversable as an (non-multi) adapter and ended up with a working test. In the actual system, we found that the traversable would not be used. After investigation we found a conditional branch in the traverse() function which would look for a multi-adapter if a request was around, and a regular adapter if not. We didn't anticipate this difference and it cost us some time, so we wonder whether this has to be the way it is, or whether this could be changed to behave more obvious and consistent. Christian and Wolfgang -- 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

8 14

Double usage of vocabulary in z3c.form seems to fail
by Hermann Himmelbauer 17 Oct '08

17 Oct '08

Hi, I currently have two schema.Choice() fields in my z3c.form - based form, that references the same vocabulary. runjobs = Choice( title = u'Job', vocabulary=('cronjobsVocabulary'), required = False) cronjobs = Choice( title = u'Periodic Jobs', vocabulary=('cronjobsVocabulary'), required = False) However, when trying to get data from this field in my ActionHandler, strange things happen: It seems that one choice field conflicts with the other, especially it seems, that only one field is used. Any clue why? How can I solve that - perhaps I should register the same vocabulary a second time under a different name? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

1 1

Re: [Zope-dev] [Checkins] SVN: zope.testing/trunk/ - Open doctest files in universal mode, so that packages released in Windoes
by Jim Fulton 17 Oct '08

17 Oct '08

testrunner-coverage.txt is failing since this check in. What's up with this? Jim On Aug 27, 2008, at 3:41 AM, Stephan Richter wrote: > Log message for revision 90401: > - Open doctest files in universal mode, so that packages released > in Windoes > can be tested in Linux, for example. > > - Fixed failing test in testrunner-coverage.txt. > --This line, and those > below, > will be ignored-- > > AM src/zope/testing/doctest.txt > M src/zope/testing/tests.py > M src/zope/testing/doctest.py > M src/zope/testing/testrunner/testrunner-coverage.txt > M README.txt > > > Changed: > U zope.testing/trunk/README.txt > U zope.testing/trunk/src/zope/testing/doctest.py > A zope.testing/trunk/src/zope/testing/doctest.txt > U zope.testing/trunk/src/zope/testing/testrunner/testrunner- > coverage.txt > U zope.testing/trunk/src/zope/testing/tests.py > > -=- > Modified: zope.testing/trunk/README.txt > =================================================================== > --- zope.testing/trunk/README.txt 2008-08-27 07:27:11 UTC (rev 90400) > +++ zope.testing/trunk/README.txt 2008-08-27 07:41:00 UTC (rev 90401) > @@ -63,6 +63,8 @@ > > - Fixed NameError in StartUpFailure. > > +- Open doctest files in universal mode, so that packages released > in Windoes > + can be tested in Linux, for example. > > > 3.6.0 (2008/07/10) > > Modified: zope.testing/trunk/src/zope/testing/doctest.py > =================================================================== > --- zope.testing/trunk/src/zope/testing/doctest.py 2008-08-27 > 07:27:11 UTC (rev 90400) > +++ zope.testing/trunk/src/zope/testing/doctest.py 2008-08-27 > 07:41:00 UTC (rev 90401) > @@ -2074,7 +2074,7 @@ > runner = DocTestRunner(verbose=verbose, > optionflags=optionflags) > > # Read the file, convert it to a test, and run it. > - s = open(filename).read() > + s = open(filename, 'U').read() > if encoding is None: > encoding = pep263_encoding(s) > if encoding is not None: > @@ -2517,7 +2517,7 @@ > > # Find the file and read it. > name = os.path.basename(path) > - doc = open(path).read() > + doc = open(path, 'U').read() > > # If an encoding is specified, use it to convert the file to > unicode > if encoding is None: > > Added: zope.testing/trunk/src/zope/testing/doctest.txt > =================================================================== > --- zope.testing/trunk/src/zope/testing/ > doctest.txt (rev 0) > +++ zope.testing/trunk/src/zope/testing/doctest.txt 2008-08-27 > 07:41:00 UTC (rev 90401) > @@ -0,0 +1,32 @@ > +======================== > +Additional doctest Tests > +======================== > + > +Most `doctest` module tests are located within the module. This > file only > +tests a few additional features not covered by the module tests, so > that the > +changes to the `doctest` module -- which is forked from the Python > stanadrd > +library -- are minimized. > + > +Working with Carriage Returns > +----------------------------- > + > +Due to the way releases are made on different platforms, we > sometimes test > +files on a *nix system with Windows file endings. Unfortunately, > that leaves > +some the tests broken: > + > + >>> import tempfile > + >>> fn = tempfile.mktemp() > + >>> open(fn, 'w').write('Test:\r\n\r\n >>> x = 1 + 1\r\n\r\nDone. > \r\n') > + > +Let's now run it as a doctest: > + > + >>> from zope.testing import doctest > + >>> doctest.testfile(fn, False) > + (0, 1) > + > +It worked. Let's also try the test file suite: > + > + >>> import unittest > + >>> result = unittest.TestResult() > + >>> doctest.DocFileSuite(fn, module_relative=False).run(result) > + <unittest.TestResult run=1 errors=0 failures=0> > > > Property changes on: zope.testing/trunk/src/zope/testing/doctest.txt > ___________________________________________________________________ > Name: svn:eol-style > + native > > Modified: zope.testing/trunk/src/zope/testing/testrunner/testrunner- > coverage.txt > =================================================================== > --- zope.testing/trunk/src/zope/testing/testrunner/testrunner- > coverage.txt 2008-08-27 07:27:11 UTC (rev 90400) > +++ zope.testing/trunk/src/zope/testing/testrunner/testrunner- > coverage.txt 2008-08-27 07:41:00 UTC (rev 90401) > @@ -52,32 +52,41 @@ > Tearing down left over layers: > Tear down zope.testing.testrunner.layer.UnitTests in 0.000 > seconds. > lines cov% module (path) > - 82 78% sample1.sample11.sampletests (testrunner-ex > \sample1\sample11\sampletests.py) > - 52 92% sample1.sample13.sampletests (testrunner-ex > \sample1\sample13\sampletests.py) > - 52 92% sample1.sampletests.test1 (testrunner-ex > \sample1\sampletests\test1.py) > - 78 94% sample1.sampletests.test11 (testrunner-ex > \sample1\sampletests\test11.py) > - 78 94% sample1.sampletests.test111 (testrunner-ex > \sample1\sampletests\test111.py) > - 78 94% sample1.sampletests.test112 (testrunner-ex > \sample1\sampletests\test112.py) > - 78 94% sample1.sampletests.test12 (testrunner-ex > \sample1\sampletests\test12.py) > - 78 94% sample1.sampletests.test121 (testrunner-ex > \sample1\sampletests\test121.py) > - 78 94% sample1.sampletests.test122 (testrunner-ex > \sample1\sampletests\test122.py) > - 52 92% sample1.sampletests.test_one (testrunner-ex > \sample1\sampletests\test_one.py) > - 52 92% sample1.sampletestsf (testrunner-ex > \sample1\sampletestsf.py) > - 52 92% sample2.sample21.sampletests (testrunner-ex > \sample2\sample21\sampletests.py) > - 52 92% sample2.sampletests.test_1 (testrunner-ex > \sample2\sampletests\test_1.py) > - 52 92% sample2.sampletests.testone (testrunner-ex > \sample2\sampletests\testone.py) > - 52 92% sample3.sampletests (testrunner-ex > \sample3\sampletests.py) > - 96 75% samplelayers (testrunner-ex\samplelayers.py) > - 52 92% sampletests.test1 (testrunner-ex\sampletests > \test1.py) > - 78 94% sampletests.test11 (testrunner-ex\sampletests > \test11.py) > - 78 94% sampletests.test111 (testrunner-ex\sampletests > \test111.py) > - 80 95% sampletests.test112 (testrunner-ex\sampletests > \test112.py) > - 78 94% sampletests.test12 (testrunner-ex\sampletests > \test12.py) > - 78 94% sampletests.test121 (testrunner-ex\sampletests > \test121.py) > - 78 94% sampletests.test122 (testrunner-ex\sampletests > \test122.py) > - 52 92% sampletests.test_one (testrunner-ex\sampletests > \test_one.py) > - 122 87% sampletestsf (testrunner-ex\sampletestsf.py) > - Total: 405 tests, 0 failures, 0 errors in 1.641 seconds. > + 1 100% sample1.__init__ (testrunner-ex/sample1/ > __init__.py) > + 1 100% sample1.sample11.__init__ (testrunner-ex/ > sample1/sample11/__init__.py) > + 74 86% sample1.sample11.sampletests (testrunner-ex/ > sample1/sample11/sampletests.py) > + 1 100% sample1.sample13.__init__ (testrunner-ex/ > sample1/sample13/__init__.py) > + 48 100% sample1.sample13.sampletests (testrunner-ex/ > sample1/sample13/sampletests.py) > + 1 100% sample1.sampletests.__init__ (testrunner-ex/ > sample1/sampletests/__init__.py) > + 48 100% sample1.sampletests.test1 (testrunner-ex/ > sample1/sampletests/test1.py) > + 74 100% sample1.sampletests.test11 (testrunner-ex/ > sample1/sampletests/test11.py) > + 74 100% sample1.sampletests.test111 (testrunner-ex/ > sample1/sampletests/test111.py) > + 74 100% sample1.sampletests.test112 (testrunner-ex/ > sample1/sampletests/test112.py) > + 74 100% sample1.sampletests.test12 (testrunner-ex/ > sample1/sampletests/test12.py) > + 74 100% sample1.sampletests.test121 (testrunner-ex/ > sample1/sampletests/test121.py) > + 74 100% sample1.sampletests.test122 (testrunner-ex/ > sample1/sampletests/test122.py) > + 48 100% sample1.sampletests.test_one (testrunner-ex/ > sample1/sampletests/test_one.py) > + 48 100% sample1.sampletestsf (testrunner-ex/sample1/ > sampletestsf.py) > + 1 100% sample2.__init__ (testrunner-ex/sample2/ > __init__.py) > + 1 100% sample2.sample21.__init__ (testrunner-ex/ > sample2/sample21/__init__.py) > + 48 100% sample2.sample21.sampletests (testrunner-ex/ > sample2/sample21/sampletests.py) > + 1 100% sample2.sampletests.__init__ (testrunner-ex/ > sample2/sampletests/__init__.py) > + 48 100% sample2.sampletests.test_1 (testrunner-ex/ > sample2/sampletests/test_1.py) > + 48 100% sample2.sampletests.testone (testrunner-ex/ > sample2/sampletests/testone.py) > + 1 100% sample3.__init__ (testrunner-ex/sample3/ > __init__.py) > + 48 100% sample3.sampletests (testrunner-ex/sample3/ > sampletests.py) > + 84 85% samplelayers (testrunner-ex/samplelayers.py) > + 1 100% sampletests.__init__ (testrunner-ex/ > sampletests/__init__.py) > + 48 100% sampletests.test1 (testrunner-ex/sampletests/ > test1.py) > + 74 100% sampletests.test11 (testrunner-ex/sampletests/ > test11.py) > + 74 100% sampletests.test111 (testrunner-ex/sampletests/ > test111.py) > + 76 100% sampletests.test112 (testrunner-ex/sampletests/ > test112.py) > + 74 100% sampletests.test12 (testrunner-ex/sampletests/ > test12.py) > + 74 100% sampletests.test121 (testrunner-ex/sampletests/ > test121.py) > + 74 100% sampletests.test122 (testrunner-ex/sampletests/ > test122.py) > + 48 100% sampletests.test_one (testrunner-ex/ > sampletests/test_one.py) > + 112 95% sampletestsf (testrunner-ex/sampletestsf.py) > + Total: 405 tests, 0 failures, 0 errors in 0.630 seconds. > False > > The directory specified with the --coverage option will have been > created and > > Modified: zope.testing/trunk/src/zope/testing/tests.py > =================================================================== > --- zope.testing/trunk/src/zope/testing/tests.py 2008-08-27 07:27:11 > UTC (rev 90400) > +++ zope.testing/trunk/src/zope/testing/tests.py 2008-08-27 07:41:00 > UTC (rev 90401) > @@ -23,10 +23,11 @@ > > def test_suite(): > return unittest.TestSuite(( > + doctest.DocTestSuite('zope.testing.loggingsupport'), > doctest.DocTestSuite('zope.testing.renormalizing'), > + doctest.DocTestSuite('zope.testing.server'), > + doctest.DocFileSuite('doctest.txt'), > doctest.DocFileSuite('formparser.txt'), > - doctest.DocTestSuite('zope.testing.loggingsupport'), > - doctest.DocTestSuite('zope.testing.server'), > + doctest.DocFileSuite('module.txt'), > doctest.DocFileSuite('setupstack.txt'), > - doctest.DocFileSuite('module.txt'), > )) > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins -- Jim Fulton Zope Corporation

2 2

Re: [Zope-dev] SVN: ZODB/trunk/buildout.cfg Changed the generated test script to use a part-local tmp directory
by Tres Seaver 17 Oct '08

17 Oct '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote: > Log message for revision 92293: > Changed the generated test script to use a part-local tmp directory > that is cleaned up at the start of a test run. > > Unfortunately, the ZODB tests leave lots of temporary files behind > which can cause failures in subsequent test runs and which tend to > litter /tmp. Eventually, I want to clean that up, but, in the mean > time, I can limit the damage to the test part directory. > > > Changed: > U ZODB/trunk/buildout.cfg > > -=- > Modified: ZODB/trunk/buildout.cfg > =================================================================== > --- ZODB/trunk/buildout.cfg 2008-10-17 12:46:34 UTC (rev 92292) > +++ ZODB/trunk/buildout.cfg 2008-10-17 14:02:39 UTC (rev 92293) > @@ -6,6 +6,11 @@ > [test] > recipe = zc.recipe.testrunner > eggs = ZODB3 > +initialization = > + import os, tempfile, shutil > + if os.path.exists('tmp'): shutil.rmtree('tmp') > + os.mkdir('tmp') > + tempfile.tempdir = os.path.abspath('tmp') > > [scripts] > recipe = zc.recipe.egg Maybe zc.recipe.testrunner could add support for a 'finalization' or 'cleanup' argument which would do the same think as the 'initialization' (or maybe only if there were no failures?) 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 iD8DBQFI+L+Y+gerLs4ltQ4RAgtjAKClCd+fCX0zjCPZD944HDJ/Tp2ZxwCgmVHM 0IMF4ykSw9OKP0ICgwPCNfg= =+qlo -----END PGP SIGNATURE-----

2 1

Re: [Zope-dev] SVN: z3c.relationfield/trunk/buildout.cfg zope.testing somehow doesn't upgrade without hardcoding it. I don't know
by Tres Seaver 17 Oct '08

17 Oct '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote: > Log message for revision 92303: > zope.testing somehow doesn't upgrade without hardcoding it. I don't know > why I keep running into it, but I am running into it absolutely all over > the place. There is a newer release of zope.testing (3.7.0); perhaps that is part of the problem? 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 iD8DBQFI+MBx+gerLs4ltQ4RAkwVAJ9vVt/OHO1JEh5g/s6gg6KSPbmIaQCfT8Z1 vVI56/ce+ezcZMzYXZgekFM= =Yycp -----END PGP SIGNATURE-----

1 0

zope.testbrowser: Newlines in textarea not always preserved
by Christian Zagrodnick 17 Oct '08

17 Oct '08

Hi, a few weeks ago I posted a bug regarding zope.testbrowser: https://bugs.launchpad.net/zope3/+bug/268139 »When there is XML or HTML-Code in the Textarea the newlines are removed.« Could anybody give me a hint how to fix it? I'd really apprechiate it because it prevents me from using Python 2.5 :) Regards, -- Christian Zagrodnick · cz(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 0

ForbiddenAttribute: why subclass AttributeError?
by Christian Theune 17 Oct '08

17 Oct '08

Hi, Why is a ForbiddenAttribute also an AttributeError? Is this intended to avoid 'information leaks'? We found a nasty side-effect together with getattr and annotations: a user that didn't have read-access to __annotations__ would end up trying to create the annotations container again and again because getattr(obj '__annotations__', None) would return None instead of propagating the ForbiddenAttribute exception. Christian and Wolfgang -- 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

2 1

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

17 Oct '08

Summary of messages to the zope-tests list. Period Thu Oct 16 11:00:00 2008 UTC to Fri Oct 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: Thu Oct 16 20:50:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010325.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Oct 16 20:52:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010326.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Oct 16 20:53:59 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010327.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Oct 16 20:55:29 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010328.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Oct 16 20:56:59 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010329.html

1 0