- Zope-Dev - Zope lists

Problems with schema Date field - year is truncated
by Hermann Himmelbauer 31 Aug '08

31 Aug '08

Hi, I'm somehow stuck on the following problem: I defined a Date() schema field in one of my interfaces. I currently have a de-AT locale, so I'd like to enter the value of my date as e.g. "dd.MM.YYYY", e.g. "01.02.1980" in my z3c.form based form. What happens is, that the locale silently assumes a format of "dd.MM.yy", which means, that the "YY / 80" is truncated and "01.02.19" is stored in my database, when updating. So, I'd like to know if: - It is possible to change the format to "dd.MM.yyyy", which is a lot more appropriate for my application (a birth date) - Make the application more strict, meaning that no data is truncated in any case. I tried to stick my nose into i18n.locales but was somehow overwhelmed by what I found. However, the following somehow seems to explain it: </dateFormatLength > <dateFormatLength type="medium"> <dateFormat > <pattern>dd.MM.yyyy</pattern> </dateFormat> </dateFormatLength > <dateFormatLength type="short"> <dateFormat > <pattern>dd.MM.yy</pattern> </dateFormat> </dateFormatLength > Nevertheless I don't know if there's a way to select a specific dateFormat, e.g. "medium" in my case. Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

2 1

z3c.form - extraction from sequence widget
by Martin Aspeli 30 Aug '08

30 Aug '08

Hi, In z3c.form.widget.SequenceWidget, we have: def extract(self, default=interfaces.NOVALUE): """See z3c.form.interfaces.IWidget.""" if (self.name not in self.request and self.name+'-empty-marker' in self.request): return [] value = self.request.get(self.name, default) if value != default: for token in value: if token == self.noValueToken: continue try: self.terms.getTermByToken(token) except LookupError: return default return value This means that if the request contains the empty-marker only (no selection was made) for a checkbox widget (say), then the return value is [], rather than default (NOVALUE). Is that a bug? I have a custom checkbox widget derived from the standard checkbox widget, (z3c.formwidget.query, in fact), and I never get any "required missing" exceptions, even when I untick all the checkboxes and click OK. Am I missing something? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

8 18

Zope Tests: 5 OK
by Zope Tests Summarizer 30 Aug '08

30 Aug '08

Summary of messages to the zope-tests list. Period Fri Aug 29 11:00:00 2008 UTC to Sat Aug 30 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: Fri Aug 29 20:52:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010085.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 29 20:53:43 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010086.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 29 20:55:14 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010087.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 29 20:56:44 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010088.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 29 20:58:14 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010089.html

1 0

ZPT and strict namespace mapping
by Malthe Borch 30 Aug '08

30 Aug '08

Trying to get a feeling here on whether we want to require proper XML namespace definition (current z3c.pt behavior) or implicitly fallback to the standard mappings (current zope.pagetemplate behavior). \malthe

5 8

Bug in z3c.form.browser.orderedselect
by Dan Korostelev 30 Aug '08

30 Aug '08

Hi, people! In the OrederedSelectWidget's input template there's a little bug in options displaying. Options (for selectedItems and notSelectedItems) are displayed using expression like this (simplified): <option tal:content="entry/content" /> Which will result in calling entry['content'] if it is callable, which is true (for example) for the standard zope's "Content Types" vocabulary from zope.app.content, because by default the term.value is used for the "content" and then, if the term provides ITitleTokenizedTerm it is replaced with translated term.title. But in the "Content Types" vocabulary, terms are not titled, so term.value is used, which is some Interface subclass and which is callable. So, as far as I understand, to fix little issue, we need to add the "nocall" modifier in the template, so option expression will look like this (simplifed): <option tal:content="nocall:entry/content" /> Thanks! PS Is there any bug tracking system for z3c.form package (like zope's general one on launchpad)? -- WBR, Dan Korostelev

2 1

Failing Zope 2.8 / Python 2.3 tests on your box
by Tres Seaver 29 Aug '08

29 Aug '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefan, Tests are blowing up on that box becaues the 'encodings' module has no attribute 'aliases': AFAICT, that doesn't happen on a "standard" build of Python: is there something weird about your setup? 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 iD8DBQFIrFr++gerLs4ltQ4RArW6AKCKRbzeFvOkI8bWuJLHswuIYeMELQCfSLB0 a3pJHstsrL2JMsZXpJRJqUw= =mAA8 -----END PGP SIGNATURE-----

3 6

Re: [Zope-dev] [Checkins] SVN: zc.recipe.testrunner/trunk/src/zc/recipe/testrunner/README.txt made doctest sections from the literal sections
by Benji York 29 Aug '08

29 Aug '08

On Mon, Aug 25, 2008 at 6:24 AM, Michael Howitz <mh(a)gocept.com> wrote: > Log message for revision 90184: > made doctest sections from the literal sections Thanks for removing the unneccesary -- and inappropriate -- double colons. However, for better or worse, the nearly universal style in zope.* code is to indent doctest blocks in stand-alone text files, so please restore the previous indentation. Thanks. > > Changed: > U zc.recipe.testrunner/trunk/src/zc/recipe/testrunner/README.txt > > -=- > Modified: zc.recipe.testrunner/trunk/src/zc/recipe/testrunner/README.txt > =================================================================== > --- zc.recipe.testrunner/trunk/src/zc/recipe/testrunner/README.txt 2008-08-25 09:41:43 UTC (rev 90183) > +++ zc.recipe.testrunner/trunk/src/zc/recipe/testrunner/README.txt 2008-08-25 10:24:35 UTC (rev 90184) > @@ -38,259 +38,259 @@ > distributions cannot be zip files. TODO: Fix the test runner!) > > To illustrate this, we'll create a pair of projects in our sample > -buildout:: > +buildout: > > - >>> mkdir(sample_buildout, 'demo') > - >>> mkdir(sample_buildout, 'demo', 'demo') > - >>> write(sample_buildout, 'demo', 'demo', '__init__.py', '') > - >>> write(sample_buildout, 'demo', 'demo', 'tests.py', > - ... ''' > - ... import unittest > - ... > - ... class TestDemo(unittest.TestCase): > - ... def test(self): > - ... pass > - ... > - ... def test_suite(): > - ... return unittest.makeSuite(TestDemo) > - ... ''') > +>>> mkdir(sample_buildout, 'demo') > +>>> mkdir(sample_buildout, 'demo', 'demo') > +>>> write(sample_buildout, 'demo', 'demo', '__init__.py', '') > +>>> write(sample_buildout, 'demo', 'demo', 'tests.py', > +... ''' > +... import unittest > +... > +... class TestDemo(unittest.TestCase): > +... def test(self): > +... pass > +... > +... def test_suite(): > +... return unittest.makeSuite(TestDemo) > +... ''') > > - >>> write(sample_buildout, 'demo', 'setup.py', > - ... """ > - ... from setuptools import setup > - ... > - ... setup(name = "demo") > - ... """) > +>>> write(sample_buildout, 'demo', 'setup.py', > +... """ > +... from setuptools import setup > +... > +... setup(name = "demo") > +... """) > > - >>> write(sample_buildout, 'demo', 'README.txt', '') > +>>> write(sample_buildout, 'demo', 'README.txt', '') > > - >>> mkdir(sample_buildout, 'demo2') > - >>> mkdir(sample_buildout, 'demo2', 'demo2') > - >>> write(sample_buildout, 'demo2', 'demo2', '__init__.py', '') > - >>> write(sample_buildout, 'demo2', 'demo2', 'tests.py', > - ... ''' > - ... import unittest > - ... > - ... class Demo2Tests(unittest.TestCase): > - ... def test2(self): > - ... pass > - ... > - ... def test_suite(): > - ... return unittest.makeSuite(Demo2Tests) > - ... ''') > +>>> mkdir(sample_buildout, 'demo2') > +>>> mkdir(sample_buildout, 'demo2', 'demo2') > +>>> write(sample_buildout, 'demo2', 'demo2', '__init__.py', '') > +>>> write(sample_buildout, 'demo2', 'demo2', 'tests.py', > +... ''' > +... import unittest > +... > +... class Demo2Tests(unittest.TestCase): > +... def test2(self): > +... pass > +... > +... def test_suite(): > +... return unittest.makeSuite(Demo2Tests) > +... ''') > > - >>> write(sample_buildout, 'demo2', 'setup.py', > - ... """ > - ... from setuptools import setup > - ... > - ... setup(name = "demo2", install_requires= ['demoneeded']) > - ... """) > +>>> write(sample_buildout, 'demo2', 'setup.py', > +... """ > +... from setuptools import setup > +... > +... setup(name = "demo2", install_requires= ['demoneeded']) > +... """) > > - >>> write(sample_buildout, 'demo2', 'README.txt', '') > +>>> write(sample_buildout, 'demo2', 'README.txt', '') > > -Demo 2 depends on demoneeded:: > +Demo 2 depends on demoneeded: > > - >>> mkdir(sample_buildout, 'demoneeded') > - >>> mkdir(sample_buildout, 'demoneeded', 'demoneeded') > - >>> write(sample_buildout, 'demoneeded', 'demoneeded', '__init__.py', '') > - >>> write(sample_buildout, 'demoneeded', 'demoneeded', 'tests.py', > - ... ''' > - ... import unittest > - ... > - ... class TestNeeded(unittest.TestCase): > - ... def test_needed(self): > - ... pass > - ... > - ... def test_suite(): > - ... return unittest.makeSuite(TestNeeded) > - ... ''') > +>>> mkdir(sample_buildout, 'demoneeded') > +>>> mkdir(sample_buildout, 'demoneeded', 'demoneeded') > +>>> write(sample_buildout, 'demoneeded', 'demoneeded', '__init__.py', '') > +>>> write(sample_buildout, 'demoneeded', 'demoneeded', 'tests.py', > +... ''' > +... import unittest > +... > +... class TestNeeded(unittest.TestCase): > +... def test_needed(self): > +... pass > +... > +... def test_suite(): > +... return unittest.makeSuite(TestNeeded) > +... ''') > > - >>> write(sample_buildout, 'demoneeded', 'setup.py', > - ... """ > - ... from setuptools import setup > - ... > - ... setup(name = "demoneeded") > - ... """) > +>>> write(sample_buildout, 'demoneeded', 'setup.py', > +... """ > +... from setuptools import setup > +... > +... setup(name = "demoneeded") > +... """) > > - >>> write(sample_buildout, 'demoneeded', 'README.txt', '') > +>>> write(sample_buildout, 'demoneeded', 'README.txt', '') > > We'll update our buildout to install the demo project as a > -develop egg and to create the test script:: > +develop egg and to create the test script: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo demoneeded demo2 > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = > - ... demo > - ... demo2 > - ... script = test > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo demoneeded demo2 > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = > +... demo > +... demo2 > +... script = test > +... """) > > Note that we specified both demo and demo2 in the eggs > option and that we put them on separate lines. > > We also specified the offline option to run the buildout in offline mode. > > -Now when we run the buildout:: > +Now when we run the buildout: > > - >>> import os > - >>> os.chdir(sample_buildout) > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> import os > +>>> os.chdir(sample_buildout) > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > -We get a test script installed in our bin directory:: > +We get a test script installed in our bin directory: > > - >>> ls(sample_buildout, 'bin') > - - buildout > - - test > +>>> ls(sample_buildout, 'bin') > +- buildout > +- test > > -We also get a part directory for the tests to run in:: > +We also get a part directory for the tests to run in: > > - >>> ls(sample_buildout, 'parts') > - d testdemo > +>>> ls(sample_buildout, 'parts') > +d testdemo > > -And updating leaves its contents intact:: > +And updating leaves its contents intact: > > - >>> _ = system(os.path.join(sample_buildout, 'bin', 'test') + > - ... ' -q --coverage=coverage') > - >>> ls(sample_buildout, 'parts', 'testdemo') > - d coverage > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > - >>> ls(sample_buildout, 'parts', 'testdemo') > - d coverage > +>>> _ = system(os.path.join(sample_buildout, 'bin', 'test') + > +... ' -q --coverage=coverage') > +>>> ls(sample_buildout, 'parts', 'testdemo') > +d coverage > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> ls(sample_buildout, 'parts', 'testdemo') > +d coverage > > -We can run the test script to run our demo test:: > +We can run the test script to run our demo test: > > - >>> print system(os.path.join(sample_buildout, 'bin', 'test') + ' -vv'), > - Running tests at level 1 > - Running unit tests: > - Running: > - test (demo.tests.TestDemo) > - test2 (demo2.tests.Demo2Tests) > - Ran 2 tests with 0 failures and 0 errors in 0.000 seconds. > +>>> print system(os.path.join(sample_buildout, 'bin', 'test') + ' -vv'), > +Running tests at level 1 > +Running unit tests: > + Running: > + test (demo.tests.TestDemo) > + test2 (demo2.tests.Demo2Tests) > + Ran 2 tests with 0 failures and 0 errors in 0.000 seconds. > > Note that we didn't run the demoneeded tests. Tests are only run for > the eggs listed, not for their dependencies. > > If we leave the script option out of the configuration, then the test > -script will get it's name from the part:: > +script will get it's name from the part: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> ls(sample_buildout, 'bin') > - - buildout > - - testdemo > +>>> ls(sample_buildout, 'bin') > +- buildout > +- testdemo > > -We can run the test script to run our demo test:: > +We can run the test script to run our demo test: > > - >>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -q'), > - Running unit tests: > - Ran 1 tests with 0 failures and 0 errors in 0.000 seconds. > +>>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -q'), > +Running unit tests: > + Ran 1 tests with 0 failures and 0 errors in 0.000 seconds. > > If we need to include other paths in our test script, we can use the > -extra-paths option to specify them:: > +extra-paths option to specify them: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... extra-paths = /usr/local/zope/lib/python > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... extra-paths = /usr/local/zope/lib/python > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - '/usr/local/zope/lib/python', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/sample-buildout/parts/testdemo') > - <BLANKLINE> > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run([ > - '--test-path', '/sample-buildout/demo', > - ]) > +>>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + '/usr/local/zope/lib/python', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/sample-buildout/parts/testdemo') > +<BLANKLINE> > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run([ > + '--test-path', '/sample-buildout/demo', > + ]) > > We can use the working-directory option to specify a working > -directory:: > +directory: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... extra-paths = /usr/local/zope/lib/python > - ... working-directory = /foo/bar > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... extra-paths = /usr/local/zope/lib/python > +... working-directory = /foo/bar > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - '/usr/local/zope/lib/python', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/foo/bar') > - <BLANKLINE> > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run([ > - '--test-path', '/sample-buildout/demo', > - ]) > +>>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + '/usr/local/zope/lib/python', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/foo/bar') > +<BLANKLINE> > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run([ > + '--test-path', '/sample-buildout/demo', > + ]) > > Now that out tests use a specified working directory, their designated > -part directory is gone:: > +part directory is gone: > > - >>> ls(sample_buildout, 'parts') > +>>> ls(sample_buildout, 'parts') > > If we need to specify default options, we can use the defaults > option. For example, Zope 3 applications typically define test suites > @@ -298,50 +298,50 @@ > is to look in modules named tests. To specify that we want to look in > tests and ftests module, we'd supply a default for the --tests-pattern > option. If we like dots, we could also request more verbose output > -using the -v option:: > +using the -v option: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... extra-paths = /usr/local/zope/lib/python > - ... defaults = ['--tests-pattern', '^f?tests$', > - ... '-v' > - ... ] > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... extra-paths = /usr/local/zope/lib/python > +... defaults = ['--tests-pattern', '^f?tests$', > +... '-v' > +... ] > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.4.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - '/usr/local/zope/lib/python', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/sample-buildout/parts/testdemo') > - <BLANKLINE> > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > - '-v' > - ]) + [ > - '--test-path', '/sample-buildout/demo', > - ]) > +>>> cat(sample_buildout, 'bin', 'testdemo') > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.4.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + '/usr/local/zope/lib/python', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/sample-buildout/parts/testdemo') > +<BLANKLINE> > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > +'-v' > +]) + [ > + '--test-path', '/sample-buildout/demo', > + ]) > > Some things to note from this example: > > @@ -351,188 +351,187 @@ > > > To demonstrate the ``environment`` option, we first update the tests to > -include a check for an environment variable:: > +include a check for an environment variable: > > - >>> write(sample_buildout, 'demo', 'demo', 'tests.py', > - ... ''' > - ... import unittest > - ... import os > - ... > - ... class DemoTests(unittest.TestCase): > - ... def test(self): > - ... self.assertEquals('42', os.environ.get('zc.recipe.testrunner', '23')) > - ... > - ... def test_suite(): > - ... return unittest.makeSuite(DemoTests) > - ... ''') > +>>> write(sample_buildout, 'demo', 'demo', 'tests.py', > +... ''' > +... import unittest > +... import os > +... > +... class DemoTests(unittest.TestCase): > +... def test(self): > +... self.assertEquals('42', os.environ.get('zc.recipe.testrunner', '23')) > +... > +... def test_suite(): > +... return unittest.makeSuite(DemoTests) > +... ''') > > -Running them with the current buildout will produce a failure:: > +Running them with the current buildout will produce a failure: > > - >>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -vv'), # doctest: +REPORT_NDIFF +ELLIPSIS > - Running tests at level 1 > - Running unit tests: > - Running: > - test (demo.tests.DemoTests) > - <BLANKLINE> > - Failure in test test (demo.tests.DemoTests) > - Traceback (most recent call last): > - ... > - raise self.failureException, \ > - AssertionError: '42' != '23' > - <BLANKLINE> > - <BLANKLINE> > - Ran 1 tests with 1 failures and 0 errors in 0.001 seconds. > - <BLANKLINE> > - Tests with failures: > - test (demo.tests.DemoTests) > +>>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -vv'), # doctest: +REPORT_NDIFF +ELLIPSIS > +Running tests at level 1 > +Running unit tests: > + Running: > + test (demo.tests.DemoTests) > +<BLANKLINE> > +Failure in test test (demo.tests.DemoTests) > +Traceback (most recent call last): > + ... > + raise self.failureException, \ > +AssertionError: '42' != '23' > +<BLANKLINE> > +<BLANKLINE> > + Ran 1 tests with 1 failures and 0 errors in 0.001 seconds. > +<BLANKLINE> > +Tests with failures: > + test (demo.tests.DemoTests) > > > Let's update the buildout to specify the environment variable for the test > -runner:: > +runner: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... environment = testenv > - ... > - ... [testenv] > - ... zc.recipe.testrunner = 42 > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... environment = testenv > +... > +... [testenv] > +... zc.recipe.testrunner = 42 > +... """) > > We run buildout and see that the test runner script now includes setting up > -the environment variable. Also, the tests pass again:: > +the environment variable. Also, the tests pass again: > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/sample-buildout/parts/testdemo') > - os.environ['zc.recipe.testrunner'] = '42' > - <BLANKLINE> > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run([ > - '--test-path', '/sample-buildout/demo', > - ]) > +>>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/sample-buildout/parts/testdemo') > +os.environ['zc.recipe.testrunner'] = '42' > +<BLANKLINE> > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run([ > + '--test-path', '/sample-buildout/demo', > + ]) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -vv'), > - Running tests at level 1 > - Running unit tests: > - Running: > - test (demo.tests.DemoTests) > - Ran 1 tests with 0 failures and 0 errors in 0.001 seconds. > +>>> print system(os.path.join(sample_buildout, 'bin', 'testdemo') + ' -vv'), > +Running tests at level 1 > +Running unit tests: > + Running: > + test (demo.tests.DemoTests) > + Ran 1 tests with 0 failures and 0 errors in 0.001 seconds. > > One can add initialization steps in the buildout. These will be added to the > -end of the script. > +end of the script: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... extra-paths = /usr/local/zope/lib/python > - ... defaults = ['--tests-pattern', '^f?tests$', > - ... '-v' > - ... ] > - ... initialization = print 'Hello all you egg-laying pythons!' > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... extra-paths = /usr/local/zope/lib/python > +... defaults = ['--tests-pattern', '^f?tests$', > +... '-v' > +... ] > +... initialization = print 'Hello all you egg-laying pythons!' > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - '/usr/local/zope/lib/python', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/sample-buildout/parts/testdemo') > - print 'Hello all you egg-laying pythons!' > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > - '-v' > - ]) + [ > - '--test-path', '/sample-buildout/demo', > - ]) > +>>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + '/usr/local/zope/lib/python', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/sample-buildout/parts/testdemo') > +print 'Hello all you egg-laying pythons!' > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > +'-v' > +]) + [ > + '--test-path', '/sample-buildout/demo', > + ]) > > -This will also work with a multi-line initialization section. > +This will also work with a multi-line initialization section: > > - >>> write(sample_buildout, 'buildout.cfg', > - ... """ > - ... [buildout] > - ... develop = demo > - ... parts = testdemo > - ... offline = true > - ... > - ... [testdemo] > - ... recipe = zc.recipe.testrunner > - ... eggs = demo > - ... extra-paths = /usr/local/zope/lib/python > - ... defaults = ['--tests-pattern', '^f?tests$', > - ... '-v' > - ... ] > - ... initialization = print 'Hello all you egg-laying pythons!' > - ... print 'I thought pythons were live bearers?' > - ... """) > +>>> write(sample_buildout, 'buildout.cfg', > +... """ > +... [buildout] > +... develop = demo > +... parts = testdemo > +... offline = true > +... > +... [testdemo] > +... recipe = zc.recipe.testrunner > +... eggs = demo > +... extra-paths = /usr/local/zope/lib/python > +... defaults = ['--tests-pattern', '^f?tests$', > +... '-v' > +... ] > +... initialization = print 'Hello all you egg-laying pythons!' > +... print 'I thought pythons were live bearers?' > +... """) > > - >>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > +>>> print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), > > - >>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > - #!/usr/local/bin/python2.4 > - <BLANKLINE> > - import sys > - sys.path[0:0] = [ > - '/sample-buildout/demo', > - '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > - '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > - '/usr/local/zope/lib/python', > - ] > - <BLANKLINE> > - import os > - sys.argv[0] = os.path.abspath(sys.argv[0]) > - os.chdir('/sample-buildout/parts/testdemo') > - print 'Hello all you egg-laying pythons!' > - print 'I thought pythons were live bearers?' > - <BLANKLINE> > - import zope.testing.testrunner > - <BLANKLINE> > - if __name__ == '__main__': > - zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > - '-v' > - ]) + [ > - '--test-path', '/sample-buildout/demo', > - ]) > - > +>>> cat(sample_buildout, 'bin', 'testdemo') # doctest: +REPORT_NDIFF > +#!/usr/local/bin/python2.4 > +<BLANKLINE> > +import sys > +sys.path[0:0] = [ > + '/sample-buildout/demo', > + '/sample-buildout/eggs/zope.testing-3.0-py2.3.egg', > + '/sample-buildout/eggs/setuptools-0.6-py1.3.egg', > + '/usr/local/zope/lib/python', > + ] > +<BLANKLINE> > +import os > +sys.argv[0] = os.path.abspath(sys.argv[0]) > +os.chdir('/sample-buildout/parts/testdemo') > +print 'Hello all you egg-laying pythons!' > +print 'I thought pythons were live bearers?' > +<BLANKLINE> > +import zope.testing.testrunner > +<BLANKLINE> > +if __name__ == '__main__': > + zope.testing.testrunner.run((['--tests-pattern', '^f?tests$', > +'-v' > +]) + [ > + '--test-path', '/sample-buildout/demo', > + ]) > \ No newline at end of file > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins > -- Benji York Senior Software Engineer Zope Corporation

3 3

Re: [Zope-dev] [Checkins] SVN: zope.size/trunk/bootstrap.py Added support to bootstrap on Jython.
by Benji York 29 Aug '08

29 Aug '08

On Wed, Aug 27, 2008 at 7:46 PM, Georgy Berdyshev <codingmaster(a)gmail.com> wrote: > Log message for revision 90507: > Added support to bootstrap on Jython. It strikes me that if you're going to be doing this for a lot of packages, you might be better off setting up an external to the canonical bootstrap script and just fixing it. It'll have to be an external to svn+ssh://svn.zope.org/repos/main/zc.buildout/trunk/bootstrap since Subversion doesn't do externals to individual files. The zope.introspector project is one example taking this approach: svn+ssh://svn.zope.org/repos/main/zope.introspector/trunk -- Benji York Senior Software Engineer Zope Corporation

2 2

Zope Tests: 4 OK, 1 Unknown
by Zope Tests Summarizer 29 Aug '08

29 Aug '08

Summary of messages to the zope-tests list. Period Thu Aug 28 11:00:00 2008 UTC to Fri Aug 29 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown ------- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Aug 28 20:43:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010080.html Tests passed OK --------------- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 28 20:44:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010081.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 28 20:46:03 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010082.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 28 20:47:33 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010083.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 28 20:49:03 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010084.html

1 0

zope.testing.doctest bug
by Chris Withers 29 Aug '08

29 Aug '08

Hi All, Here's an example from a python interpretter session: Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> def test(): ... print "hello" ... raise Exception() ... >>> test() hello Traceback (most recent call last): File "<stdin>", line 1, in ? File "<stdin>", line 3, in test Exception ...which doesn't behave the same as a doctest: Failed example: test() Exception raised: Traceback (most recent call last): File "zope.testing-3.6.0-py2.4.egg\zope\te sting\doctest.py", line 1356, in __run File "<doctest readme.txt[8]>", line 1, in ? test() File "<doctest readme.txt[7]>", line 3, in test raise Exception() Exception The problem is that the function prints output before raising the exception. If I take the printed output away, the doctest passes fine. However, especially with dumym fixtures common in doctests, that printed output needs to be seen to test that things are happening as they should prior to the exception being raised. Where should I log this bug? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2