- Zope-Dev - Zope lists

Re: [Zope-dev] SVN: Zope2.buildout/trunk/setup.py First round of minimizing our dependency set to the correct one.
by Tres Seaver 14 Nov '08

14 Nov '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Hanno Schlichting wrote: >> Log message for revision 92938: >> First round of minimizing our dependency set to the correct one. > > For future changes can you please not reindent the code at the same > time? It is impossible to see what changed now. > > Wichert. > This might help: $ svn diff -r 92937:92938 -x -uw \ svn+ssh://svn.zope.org/repos/main/Zope2.buildout/trunk 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 iD8DBQFJHfjs+gerLs4ltQ4RAjGaAKCovre6sMBkXYDeZd5FXC+K62UxdQCggc2n zO8oLiHwaiCPuM5VOTUSs9Y= =4Ro/ -----END PGP SIGNATURE-----

1 0

Subversion merge tracking
by Benji York 14 Nov '08

14 Nov '08

I'd like for us to disallow pre-1.5 Subversion clients from making commits starting one year from now (or sooner if there is consensus). The recent hardware problems for svn.zope.org had the positive outcome of precipitating an upgrade to Subversion 1.5 which has merge tracking. One of the requirements to use merge tracking is that no pre-1.5 client merge to the branch that you want to use with merge tracking. That means that as of now, anyone can use merge tracking on their projects as long as all merges are done with a mergeinfo-capable (1.5+) client. Until we ban commits from pre-1.5 clients (using a pre-commit hook), anyone who wants to use merge tracking will have to be careful with the clients they use (and watch out for rouge merges from other contributors which can be fixed-up after the fact). The Subversion book includes information about merge tracking: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html A description of the pre-1.5 client problem is at http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.br… -- Benji York Senior Software Engineer Zope Corporation

5 7

zope.security and zope.location depend on each other
by Joachim König 14 Nov '08

14 Nov '08

Hello, while trying to install zope.location (3.4.0) and zope.security (3.5.2) from source (in order to create a NetBSD-pkgsrc package) I noticed, that they specify each other in their install-requires list in setup.py. Looking at the code, they also import each other: > zope/location/location.py: from zope.security.decorator import DecoratedSecurityCheckerDescriptor > zope/security/adapter.py: from zope.location import ILocation, LocationProxy This is only required at runtime, so this is not a (circular) build or install dependency, but as the NetBSD-pkgsrc build infrastructure wants to generate the .pyc/.pyo files at installation time, I still have a problem with that. So my question is: Is this circular dependency really needed or could it be avoided somehow? It at least looks a bit strange to me. Two components should not depend on each other, or am I missing something? Joachim

2 1

PyPI mirrors available
by Andreas Jung 14 Nov '08

14 Nov '08

Hi there, I would like to point out that we have started the PyPI replication project some months ago during the Blackforest sprint: http://www.openplans.org/projects/pypi-mirroring/project-home As an outcome we are now able to provide in phase one of the project some mirrors of PyPI index. Currently we have three mirrors up and running and some more mirrors will join the project soon. Right now we provide all packages of PyPI that are directly hosted on PyPI (no packages with external download URLs). This project should bring a lot of ease to buildout users because PyPI is no longer a single-point-of-failure. Currently you have to choose a PyPI mirror manually. For the next project phase we think about a smarter mirror selection mechanism that is more transparent to setuptools and zc.buildout. Suggestions and further support in terms of hardware resources and bandwidth are highly appreciated. Credits go to Josip Delic and Gottfried Ganssauge of Haufe Mediengruppe for their contributions to the original codebase of z3c.pypimirror and to Daniel Kraft of D9T for being doing most of the coding of the package. 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

3 2

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 14 Nov '08

14 Nov '08

Summary of messages to the zope-tests list. Period Thu Nov 13 12:00:00 2008 UTC to Fri Nov 14 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Thu Nov 13 20:38:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010482.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Thu Nov 13 20:39:58 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010483.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Thu Nov 13 20:32:26 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010478.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Thu Nov 13 20:33:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010479.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Thu Nov 13 20:35:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010480.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Thu Nov 13 20:36:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010481.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 13 Nov '08

13 Nov '08

Summary of messages to the zope-tests list. Period Wed Nov 12 12:00:00 2008 UTC to Thu Nov 13 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:39:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010476.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Wed Nov 12 20:41:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010477.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Nov 12 20:33:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010472.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:35:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010473.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:36:40 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010474.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Nov 12 20:38:10 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010475.html

1 0

Change the CVS repository to read-only
by Jim Fulton 12 Nov '08

12 Nov '08

It appears that no one has committed to the CVS repository in almost 2 years. I propose to change it to read-only. Any objections? Jim -- Jim Fulton Zope Corporation

2 1

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 12 Nov '08

12 Nov '08

Summary of messages to the zope-tests list. Period Tue Nov 11 12:00:00 2008 UTC to Wed Nov 12 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 11 20:34:55 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010470.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Tue Nov 11 20:36:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010471.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Tue Nov 11 20:28:54 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010466.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 11 20:30:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010467.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 11 20:31:55 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010468.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 11 20:33:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010469.html

1 0

Re: [Zope-dev] [Zope-tests] FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
by Stefan H. Holek 12 Nov '08

12 Nov '08

This looks very much like zope.testbrowser 3.5.1 not passing its own tests. Sidnei, are you listening? Stefan On 12. Nov 2008, at 02:34, Zope Tests wrote: > Zope Tests : FAILED (failures=2) > Zope-trunk Python-2.4.5 : Linux > > Running /usr/local/python2.4/bin/python test.py -q --all > Running unit tests: > /home/stefan/autotest/temp/python24-zope212/lib/python/ > DocumentTemplate/DT_Raise.py:63: DeprecationWarning: String > exceptions are deprecated starting with Python 2.5 and will be > removed in a future release > t, v = upgradeException(t, v) > The following test left new threads behind: > testABOR (zope.server.ftp.tests.test_ftpserver.Tests) > New thread(s): [<_DummyThread(Dummy-39, started daemon)>, > <_DummyThread(Dummy-38, started daemon)>] > Ran 5679 tests with 0 failures and 0 errors in 3 minutes 17.322 > seconds. > Running OFS.tests.testCopySupportEvents.EventLayer tests: > Set up OFS.tests.testCopySupportEvents.EventLayer in 0.566 seconds. > Ran 14 tests with 0 failures and 0 errors in 0.161 seconds. > Running Testing.ZopeTestCase.layer.ZopeLite tests: > Tear down OFS.tests.testCopySupportEvents.EventLayer in 0.069 > seconds. > Set up Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. > Ran 626 tests with 0 failures and 0 errors in 23.137 seconds. > Running Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer tests: > Set up Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in > 0.005 seconds. > Ran 18 tests with 0 failures and 0 errors in 0.121 seconds. > Running > Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer tests: > Tear down Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in > 0.004 seconds. > Set up > Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in > 0.003 seconds. > Ran 2 tests with 0 failures and 0 errors in 0.021 seconds. > Running zope.formlib.tests.FormlibLayer tests: > Tear down > Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in > 0.003 seconds. > Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. > Set up zope.formlib.tests.FormlibLayer in 1.455 seconds. > Ran 5 tests with 0 failures and 0 errors in 0.015 seconds. > Running zope.testbrowser.tests.TestBrowserLayer tests: > Tear down zope.formlib.tests.FormlibLayer in 0.008 seconds. > Set up zope.testbrowser.tests.TestBrowserLayer in 1.321 seconds. > > > Failure in test /home/stefan/autotest/temp/python24-zope212/lib/ > python/zope/testbrowser/README.txt > Failed doctest test for README.txt > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/README.txt", line 0 > > ---------------------------------------------------------------------- > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/README.txt", line 1162, in README.txt > Failed example: > print browser.contents, > Expected: > CONTENT_LENGTH: 13 > HTTP_USER_AGENT: Python-urllib/2.4 > HTTP_CONNECTION: close > HTTP_COOKIE: > HTTP_REFERER: localhost > HTTP_ACCEPT_LANGUAGE: en-US > REQUEST_METHOD: POST > HTTP_HOST: localhost > PATH_INFO: /@@echo.html > CONTENT_TYPE: application/x-javascipt > SERVER_PROTOCOL: HTTP/1.1 > Body: '{"x":1,"y":2}' > Got: > CONTENT_LENGTH: 13 > HTTP_USER_AGENT: Python-urllib/2.4 > HTTP_CONNECTION: close > HTTP_COOKIE: > HTTP_REFERER: localhost > HTTP_ACCEPT_LANGUAGE: en-US > REQUEST_METHOD: POST > HTTP_HOST: localhost > PATH_INFO: /@@echo.html > CONTENT_TYPE: application/x-javascipt > SERVER_PROTOCOL: HTTP/1.1 > QUERY_STRING: > Body: '' > > > > Failure in test /home/stefan/autotest/temp/python24-zope212/lib/ > python/zope/testbrowser/fixed-bugs.txt > Failed doctest test for fixed-bugs.txt > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/fixed-bugs.txt", line 0 > > ---------------------------------------------------------------------- > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/fixed-bugs.txt", line 87, in fixed-bugs.txt > Failed example: > browser.open('http://localhost/@@/testbrowser/fragment.html#asdf') > Exception raised: > Traceback (most recent call last): > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testing/doctest.py", line 1356, in __run > compileflags, 1) in test.globs > File "<doctest fixed-bugs.txt[22]>", line 1, in ? > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testbrowser/browser.py", line 231, in open > self.mech_browser.open(url, data) > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > mechanize/_mechanize.py", line 177, in open > return self._mech_open(url, data) > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > mechanize/_mechanize.py", line 219, in _mech_open > raise error > HTTPError: HTTP Error 404: Not Found > ---------------------------------------------------------------------- > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/fixed-bugs.txt", line 90, in fixed-bugs.txt > Failed example: > browser.getLink('Follow me') > Exception raised: > Traceback (most recent call last): > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testing/doctest.py", line 1356, in __run > compileflags, 1) in test.globs > File "<doctest fixed-bugs.txt[24]>", line 1, in ? > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testbrowser/browser.py", line 313, in getLink > return Link(self.mech_browser.find_link(**args), self) > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > mechanize/_mechanize.py", line 499, in find_link > raise LinkNotFoundError() > LinkNotFoundError > ---------------------------------------------------------------------- > File "/home/stefan/autotest/temp/python24-zope212/lib/python/zope/ > testbrowser/fixed-bugs.txt", line 92, in fixed-bugs.txt > Failed example: > browser.getLink('Follow me').click() > Exception raised: > Traceback (most recent call last): > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testing/doctest.py", line 1356, in __run > compileflags, 1) in test.globs > File "<doctest fixed-bugs.txt[25]>", line 1, in ? > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > zope/testbrowser/browser.py", line 313, in getLink > return Link(self.mech_browser.find_link(**args), self) > File "/home/stefan/autotest/temp/python24-zope212/lib/python/ > mechanize/_mechanize.py", line 499, in find_link > raise LinkNotFoundError() > LinkNotFoundError > > Ran 114 tests with 2 failures and 0 errors in 3.044 seconds. > Running zope.traversing.tests.layer.TraversingLayer tests: > Tear down zope.testbrowser.tests.TestBrowserLayer in 0.008 seconds. > Set up zope.traversing.tests.layer.TraversingLayer/home/stefan/ > autotest/temp/python24-zope212/lib/python/zope/configuration/ > config.py:197: DeprecationWarning: ZopeSecurityPolicy is > deprecated. It has moved to zope.securitypolicy.zopepolicy This > reference will be removed somedays > obj = getattr(mod, oname) > in 1.218 seconds. > Ran 7 tests with 0 failures and 0 errors in 0.449 seconds. > Tearing down left over layers: > Tear down zope.traversing.tests.layer.TraversingLayer in 0.008 > seconds. > Total: 6465 tests, 2 failures, 0 errors in 3 minutes 59.117 seconds. > > FAILED (failures=2) > _______________________________________________ > Zope-tests mailing list > Zope-tests(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-tests -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams

2 1

Removing ZopeUndo from ZODB, starting with ZODB 3.9
by Jim Fulton 11 Nov '08

11 Nov '08

I swear I remember discussing this a while back but I can't find an email trail.... I'm going to remove ZopeUndo from ZODB, starting with 3.9. Zope 2 already has a copy (well, an external from a ZODB tag) and if someone needs it to be in a ZEO server for Zope 2 applications, they can make an egg for it and include the egg in the ZEO server. Jim -- Jim Fulton Zope Corporation

1 0