March 2004 - Zope-Dev

running test.py with instance_home products.
by Chris McDonough 03 Mar '04

03 Mar '04

Has anyone found a reasonable strategy for using Zope's test.py to test products that are installed outside the Zope software home? I try running it from the software home and using the --dir option to point it to where my product is, but it tells me it can't find any tests. - C

5 6

RE: python.exe vs pythonw.exe difference?
by Tim Peters 03 Mar '04

03 Mar '04

[moving this from comp.lang.python to zope-dev; it really belongs on a Zope list, although schemes to change what pythonw does probably belong on python-dev] [Emile van Sebille <emile(a)fenx.com>] >> I've possibly narrowed a problem I'm having running zope as a service >> on winxp pro sp 1 in that when started from a command line as: >> >> c:\zope\v27\lib\python\python.exe \ c:\zope\v27\lib\python\zope\startup\run.py -C \ c:\zope\v27\instance\etc\zope.conf [tim inserted backslashes above, to make the line structure clear] >> it starts up just fine (although now running from the console). >> >> But when I start it with: >> >> c:\zope\v27\lib\python\pythonw.exe \ c:\zope\v27\lib\python\zope\startup\run.py -C \ c:\zope\v27\instance\etc\zope.conf >> >> it dies after about 30 seconds. >> >> It wouldn't surprise me that I'm doing something it doesn't like (I'm >> spawning additional processes from within a product but it worked >> fine with 2.5), It's unclear what "it" means, in "it wworked fine with 2.5". For example, do you mean that the second command line, using pythonw.exe explicitly from a DOS box worked fine, or do you mean that running Zope as a service on XP Pro SP1 worked fine, or ...? >> but I'm somewhat at a loss as to debugging it in> that when run as a >> console app it works fine, but when run windowless it doesn't. Did you look in your Zope log file(s) for tracebacks? >> Do I have to write out check points to a file? or is there some way >> to use Mark Hammonds process debugging tools? Or is this a bug, >> known or otherwise? [Thomas Heller] > It has been reported that writing to the original sys.stdout (and > maybe also sys.stderr) sooner or later raises an IOError when running > pythonw.exe, unless these are redirected. Could this be the problem? It could, although I have no idea what WinXP does (and don't have access to XP). Here's a Python program to try: """ import sys if 1: # edit to 1 for stdout, 0 for stderr console = sys.stdout else: console = sys.stderr import traceback tb = file('tb.txt', 'w') try: i = 0 while True: i += 1 console.write('.') except: print >> tb, "Died when trying to write byte", i traceback.print_exc(file=tb) tb.close() """ Under Win98SE, and regardless of whether it writes to stdout or stderr, it dies when run under pythonw, and tb.txt contains this after: Died when trying to write byte 4097 Traceback (most recent call last): File "wr.py", line 14, in ? console.write('.') IOError: [Errno 9] Bad file descriptor The point of pythonw.exe is that no console is created or inherited, and the default stdin, stdout and stderr provided by MS C in that case are unusable (although the output flavors can appear to be usable until some secret MS limit is exceeded -- at least under Win98SE).

5 5

Zope 2.7 date international configuration
by Santi Camps 02 Mar '04

02 Mar '04

Hi all, I'm just beginning to move my applications to Zope 2.7 and I've found something estrange related to dates. In the new zope.conf you can enable an option: "datetime-format international" I've enabled it hoping that fields named field_name:date will be handled as dates in international format. But not, they are handled as dates in "us" format. Seeing the ZPublisher/Converters.py I see that fields in the form field_name:date_international are handled OK. But fields with just ":date" are hanled with default DateTime format. Seeing DateTime module, it seems that this default format should be in an environment variable DATETIME_FORMAT. Also, it seems that this variable should be defined during Zope startup. But the result is that with :date fields, "us" format is always used, not following the instruction in zope.conf. Perhaps there is some problem in Zope configuration machinery. Anybody else with this problem ? -- Santi Camps http://zetadb.sourceforge.net

3 2

Slow FTP Downloads - Zope 2.6.4, 2.7
by Edward Pollard 01 Mar '04

01 Mar '04

Some of you might recognize this thread from the zope(a)zope.org mailing list. With great reluctance smothered by desperation I thought it might be fruitful to disseminate it on this list as well. We have been using Zope 2.6.0 for some time. When we decided an upgrade was in order (to get away from ZODB killing maintenance tools), we moved to Zope 2.6.2, as that was what was available at the time. At the tail end of that upgrade, we discovered some crippling FTP bugs which seem to have been acknowledged and fixed in later revisions. Attempts to move to Zope 2.6.4 and 2.7 have been stymied, however, since any servers we have set up with these versions of Zope refuse to allow users to download via FTP faster than 10k/second. During these downloads, the CPU shoots straight to 100%. While we can have 10 different connections active, they all go at 10k/sec and the CPU is always at 100% regardless of how many connections we have. This is across a variety of FTP clients, so we don't think that is related to the issue. Experiments with the Profiler have been fruitless, and lack of experience with strace has blocked any progression at locating this problem with that, aside from noting an tremendous amount of failed open and stat64 calls - but since these are also in 2.6.0 I am not inclined to believe them significant to this problem. The server is a Dell Poweredge 1750 single processor 2.4GHz P4 Xeon with hyper-threading. RedHat 9 is running on the hardware mirrored internal HD, Zope on a NFS mounted (via TCP) volume. Moving Zope to the local disk and disabling hyper-threading has had no impact on this problem. So far, all I've been able to determine is that nobody else is having this problem. My mom always said I was special. Anyone with thoughts not previously shared on the other list? My only option at this point seems to be to go back to 2.6.0 while keeping later revisions on the ZODB tools. An inability to eventually rectify this problem would be pretty hard blow against using Zope at our institution, however, so I'm trying to avoid seriously contemplating that decision since I've grown so fond of Zope. --- Edward J. Pollard, B.Sc Webmaster, University of Lethbridge

1 0

Usability tweaks
by Christian Theune 01 Mar '04

01 Mar '04

Hi, as I'm tweaking stuff here and there right now, I stumbled over the findSupport dtml that has a multiple select menu with a height of 4. It's almost impossible to find what you look for easily. Increasing the height to 8 would be good. Anything against that? Christian PS: Anything against simply doing those small changes? -- Christian Theune, gocept gmbh & co. kg http://www.gocept.com - ct(a)gocept.com fon: 03496 3099112 fax: 03496 3099118 mobile: 0179 7808366

2 1

Zope 2.7 tutorial
by Christian Theune 01 Mar '04

01 Mar '04

Hi, gocept hired a new developer and thus I send him dig through the Zope tutorial at first. He gave me a list of bugs he found in the tutorial which we corrected here. Therefore I'll update the tutorial in the 2.7 branch in the next days. I'd updated it in 2.8 (HEAD) as well but it is severely broken in there (can't even create a tutorial). Cheers, Christian -- Christian Theune, gocept gmbh & co. kg http://www.gocept.com - ct(a)gocept.com fon: 03496 3099112 fax: 03496 3099118 mobile: 0179 7808366

2 1