December 2005 - Zope-Dev

zLOG deprecation?
by Chris Withers 08 Dec '05

08 Dec '05

Hi All, Is zLOG deprecated? If not, it should be... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

5 12

New testrunner on the Zope 2 trunk.
by Jim Fulton 07 Dec '05

07 Dec '05

I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt. Note that the new test runner complains if test_suite functions don't return test suites. There is a zope.i18n test suite that it currently complains about. Unfortunately, I can't just fix this because it is an svn:external and it will be too painful to create a tag with the necessary fix in the short term. I expect we will be integrating a newer version of Zope 3 later in the week and we'll take care of this then. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

3 11

Zope tests: 8 OK
by Zope tests summarizer 07 Dec '05

07 Dec '05

Summary of messages to the zope-tests list. Period Tue Dec 6 12:01:02 2005 UTC to Wed Dec 7 12:01:02 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:15:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003730.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:17:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003731.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:18:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003732.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:20:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003733.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:21:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003734.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:23:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003735.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:24:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003736.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:26:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003737.html

1 0

version.txt [was: make sdist]
by Philipp von Weitershausen 06 Dec '05

06 Dec '05

Andreas Jung wrote: > make sdist: > > ajung@sentinel:~/sandboxes/Zope-2.9/2.9.0b1: make sdist > zpkg -C /develop/sandboxes/Zope-2.9/2.9.0b1/releases/Zope2.cfg > 'version.txt' doesn't match any files in <collection> > (in /develop/sandboxes/Zope-2.9/2.9.0b1/lib/python/zope/app/PACKAGE.cfg) > ---- > temporary files are in /tmp/zpkg-50vtPj > make: *** [sdist] Error 1 This is a very recent problem and a result of Jim's inconsistent handling of the "version.txt" matter yesterday. http://dev.zope.org/Zope3/MakingARelease says that zope.app/version.txt should be created on a tag and zope.app/PACKAGE.cfg should also be modified to include version.txt *on the tag*. Jim did the latter on the Zope 3.2 branch. The Zope 2.9 externals currently point to the Zope 3.2 branch which references version.txt in PACKAGE.cfg but doesn't have one. Only the 3.2.0beta1 tag has it. I think that a) zope.app/PACKAGE.cfg should not mention version.txt when there isn't one, meaning on the branch b) Zope 2.9 externals should now point to the Zope 3.2.0beta1 tag. By the way, this issue reminds me: We haven't figured out how to handle Zope 2's version.txt at all! I totally forgot about it. Zope 2 expects a version.txt in Zope/lib/python, but zpkg has no way to support a data file that isn't in a Python package. So there would be no way to package it nor to install it (I don't think distutils knows how to install a non-package-related datafile either). I propose that the future place for Zope 2's version.txt is the Zope2 package. Some code inside Zope 2 that reads version info from version.txt would have to be changed for that, though. This should be fixed for the 2.9 beta, meaning today. I'm outside svn+ssh access range right now, so either you do it, Andreas, or you wait until I'm at home in about 5 hours. Philipp ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 5

Re: SVN: Zope/branches/2.9/ deprecated FastCGI
by Philipp von Weitershausen 06 Dec '05

06 Dec '05

Andreas Jung wrote: > Log message for revision 40469: > deprecated FastCGI > > > Changed: > U Zope/branches/2.9/doc/CHANGES.txt > U Zope/branches/2.9/doc/WEBSERVER.txt > U Zope/branches/2.9/lib/python/ZServer/datatypes.py > [snip] > Modified: Zope/branches/2.9/lib/python/ZServer/datatypes.py > =================================================================== > --- Zope/branches/2.9/lib/python/ZServer/datatypes.py 2005-12-02 13:45:58 UTC (rev 40468) > +++ Zope/branches/2.9/lib/python/ZServer/datatypes.py 2005-12-02 13:49:55 UTC (rev 40469) > @@ -132,6 +132,11 @@ > > class FCGIServerFactory(ServerFactory): > def __init__(self, section): > + > + import warnings > + warnings.warn("Using FastCGI is deprecated. You should use mod_proxy " > + "to run Zope with Apache", DeprecationWarning) > + > import socket > if section.address.family == socket.AF_INET: > address = section.address.address Andreas, this checkin made the tests fail for the build-bot (http://mail.zope.org/pipermail/zope-tests/2005-December/003728.html) Since you didn't use stacklevel=2 in the warnings.warn() call, it's hard to see where FCGIServerFactory() is called from. Maybe tests? Philipp

1 2

Re: [Zope-dev] Please vote about conflict errors logging
by Dario Lopez-Kästen 06 Dec '05

06 Dec '05

> 1. Do you want these ConflictErrors retried logs to be at level: INFO > 2. In addition, please specify if you feel those retried > ConflictErrors should have their full traceback logged? no traceback > 3. Finally, please tell us if the ConflictErrors that *can't* be > retried (and are returned to the user as an error, and are also > logged to the error_log) should be additionally explicitely logged to > the event log, and at which level: Yes, at ERROR level /dario _______________________________________________ Zope-Dev maillist - Zope-Dev(a)zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- -- ------------------------------------------------------------------- Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech. Lyrics applied to programming & application design: "emancipate yourself from mental slavery" - redemption song, b. marley

1 0

Zope tests: 7 OK, 1 Failed
by Zope tests summarizer 06 Dec '05

06 Dec '05

Summary of messages to the zope-tests list. Period Mon Dec 5 12:01:01 2005 UTC to Tue Dec 6 12:01:01 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:24:18 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003728.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:15:18 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003722.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:16:48 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003723.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:18:18 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003724.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:19:48 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003725.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:21:18 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003726.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:22:48 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003727.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Mon Dec 5 22:25:48 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003729.html

1 0

Ignoring Warnings
by Chris Withers 06 Dec '05

06 Dec '05

Great, so rather than fix the warnings, we add code to ignore them... *sigh* Chris Stefan H. Holek wrote: > Update of /cvs-repository/Zope > In directory cvs.zope.org:/tmp/cvs-serv6383 > > Modified Files: > Tag: Zope-2_7-branch > test.py > Log Message: > Implemented a --nowarnings flag for test.py. > Makes running CMF and Plone tests a lot less annoying. > > Usage: ./bin/zopectl test --keepbytecode --nowarnings --dir Products/CMFPlone > > > === Zope/test.py 1.2.2.19 => 1.2.2.20 === > --- Zope/test.py:1.2.2.19 Tue Oct 4 14:22:40 2005 > +++ Zope/test.py Sat Dec 3 09:31:33 2005 > @@ -104,6 +104,9 @@ > Keep running the selected tests in a loop. You may experience > memory leakage. > > +--nowarnings > + Install a filter to suppress warnings emitted by code. > + > -t > Time the individual tests and print a list of the top 50, sorted from > longest to shortest. > @@ -740,6 +743,7 @@ > global test_dir > global config_file > global import_testing > + global no_warnings > > if argv is None: > argv = sys.argv > @@ -767,11 +771,12 @@ > test_dir = None > config_file = None > import_testing = False > + now_warnings = False > > try: > opts, args = getopt.getopt(argv[1:], "a:bcC:dDfg:G:hLmprtTuv", > ["all", "help", "libdir=", "times=", > - "keepbytecode", "dir=", > + "keepbytecode", "nowarnings", "dir=", > "config-file=", "import-testing"]) > except getopt.error, msg: > print msg > @@ -843,6 +848,12 @@ > config_file = v > elif k == '--import-testing': > import_testing = True > + elif k == '--nowarnings': > + no_warnings = True > + > + if no_warnings: > + import warnings > + warnings.simplefilter('ignore', Warning, append=1) > > if gcthresh is not None: > if gcthresh == 0: > > _______________________________________________ > Zope-Checkins maillist - Zope-Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-checkins > -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

Re: SVN: Zope/tags/2.9.0b1/2.9/ Zope 2.9.0 b1
by Florent Guillaume 06 Dec '05

06 Dec '05

Andreas Jung wrote: > Log message for revision 40580: > Zope 2.9.0 b1 > > Changed: > A Zope/tags/2.9.0b1/2.9/ > > -=- > Copied: Zope/tags/2.9.0b1/2.9 (from rev 40579, Zope/branches/2.9) > Huh, did you really want to do that? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 0

AcceleratedHTTPCache and virtual hosting (collector 1447)
by Paul Winkler 06 Dec '05

06 Dec '05

Hi folks, need some advice here. http://www.zope.org/Collectors/Zope/1447 ("AcceleratedHTTPCacheManager doesn't PURGE correctly for virtual hosts") has been assigned to me like forever, and I've determined to not let another year go by with this one unfixed ;-) I'd like to apply the patch and commit, once I'm sure it works correctly, but - drumroll - AcceleratedHTTPCacheManager has no test suite at all. Which means, as frequently happens with Zope 2, I have to go through the pain of setting up a test suite for the current behavior before I go changing anything. The fun thing about this is that AcceleratedHTTPCache uses httplib to send purge notifications. I don't fancy launching a dummy server of some sort. So, I'm asking for advice: How in general does one go about setting up a unit test for network client code? One thought that occurs to me is to replace httplib.HTTPConnection with a mock object of some sort that allows easy verification of its input. So we assume that httplib works, as a proper unit test should I think. How to do this? One idea is to monkeypatch httplib during the course of the test case, and replace and then when the test finishes, restore the old httplib.HTTPConnection. But this idea smells pretty bad to me. Another thought: Maybe before doing anything else, I should make the client class used by AcceleratedHTTPCache configurable, so I can more easily get a mock in there. Something like: class AcceleratedHTTPCache (Cache): client_class = httplib.HTTPConnection ... def ZCache_invalidate(self, ob): ... h = self.client_class(host) ... Then I can just do something like this during afterSetUp(): cache = AcceleratedHTTPCache() cache.client_class = MockHTTPConnection Any better ideas? testing-network-stuff-hurts-my-head-ly-yrs, -- Paul Winkler http://www.slinkp.com

7 7