- Zope-Dev - Zope lists

Zope Tests: 5 OK
by Zope Tests Summarizer 10 May '07

10 May '07

Summary of messages to the zope-tests list. Period Wed May 9 12:00:00 2007 UTC to Thu May 10 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed May 9 20:53:06 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007704.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed May 9 20:54:37 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007705.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed May 9 20:56:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007706.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed May 9 20:57:39 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007707.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed May 9 20:59:10 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007708.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 09 May '07

09 May '07

Summary of messages to the zope-tests list. Period Tue May 8 12:00:00 2007 UTC to Wed May 9 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue May 8 20:55:55 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007699.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue May 8 20:57:26 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007700.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 20:58:57 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007701.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 21:00:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007702.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue May 8 21:02:00 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007703.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 08 May '07

08 May '07

Summary of messages to the zope-tests list. Period Mon May 7 12:00:00 2007 UTC to Tue May 8 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon May 7 20:51:27 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007694.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon May 7 20:52:58 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007695.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon May 7 20:54:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007696.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon May 7 20:55:59 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007697.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon May 7 20:57:30 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007698.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 07 May '07

07 May '07

Summary of messages to the zope-tests list. Period Sun May 6 12:00:00 2007 UTC to Mon May 7 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun May 6 20:51:22 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007689.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun May 6 20:52:52 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007690.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun May 6 20:54:23 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007691.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun May 6 20:55:54 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007692.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun May 6 20:57:25 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007693.html

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 07 May '07

07 May '07

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1474 Blamelist: benji_york,jacobholm,jim,tseaver BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 06 May '07

06 May '07

Summary of messages to the zope-tests list. Period Sat May 5 12:00:00 2007 UTC to Sun May 6 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat May 5 20:53:19 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007684.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat May 5 20:54:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007685.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat May 5 20:56:21 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007686.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat May 5 20:57:52 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007687.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat May 5 20:59:23 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007688.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 05 May '07

05 May '07

Summary of messages to the zope-tests list. Period Fri May 4 12:00:00 2007 UTC to Sat May 5 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri May 4 20:50:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007679.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri May 4 20:52:21 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007680.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri May 4 20:53:52 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007681.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri May 4 20:55:22 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007682.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri May 4 20:56:53 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-May/007683.html

1 0

Re: SVN: Zope/trunk/ Support for using zopectl on Windows has been added.
by Hanno Schlichting 04 May '07

04 May '07

Hi. I have just recently been given zope.org SVN write access and made my first bigger change - making zopectl work on Windows. Please review and test my changes. The change I made is based on code that I had in the plone.recipe.zope2instance buildout recipe and has seen quite some use by various developers, so should be reasonable stable. Hanno Hanno Schlichting wrote: > Log message for revision 75066: > Support for using zopectl on Windows has been added. All commands are supported and there are two Windows specific ones: install and remove, which install or remove the Windows service. The start, stop and restart commands handle the Windows service. > > > Changed: > U Zope/trunk/doc/CHANGES.txt > U Zope/trunk/lib/python/Zope2/Startup/zopectl.py > A Zope/trunk/skel/bin/zopectl.bat.in > > -=- > Modified: Zope/trunk/doc/CHANGES.txt > =================================================================== > --- Zope/trunk/doc/CHANGES.txt 2007-05-03 18:27:55 UTC (rev 75065) > +++ Zope/trunk/doc/CHANGES.txt 2007-05-03 18:35:20 UTC (rev 75066) > @@ -51,6 +51,12 @@ > > Features added > > + - Support for using zopectl on Windows has been added. All commands are > + supported and there are two Windows specific ones: install and remove, > + which install or remove the Windows service. The start, stop and > + restart commands handle the Windows service. In order to use them, you > + need to call 'bin\zopectl install' once. > + > - ZCatalog result objects (catalog brains) now have an interface, > ZCatalog.interfaces.ICatalogBrain. > > > Modified: Zope/trunk/lib/python/Zope2/Startup/zopectl.py > =================================================================== > --- Zope/trunk/lib/python/Zope2/Startup/zopectl.py 2007-05-03 18:27:55 UTC (rev 75065) > +++ Zope/trunk/lib/python/Zope2/Startup/zopectl.py 2007-05-03 18:35:20 UTC (rev 75066) > @@ -48,6 +48,9 @@ > from ZConfig.components.logger.handlers import FileHandlerFactory > from ZConfig.datatypes import existing_dirpath > > +WIN = False > +if sys.platform[:3].lower() == "win": > + WIN = True > > def string_list(arg): > return arg.split() > @@ -127,6 +130,12 @@ > self.python = sys.executable > self.zdrun = os.path.join(os.path.dirname(zdaemon.__file__), > "zdrun.py") > + if WIN: > + # Add the path to the zopeservice.py script, which is needed for > + # some of the Windows specific commands > + servicescript = os.path.join(self.directory, 'bin', 'zopeservice.py') > + self.servicescript = '"%s" %s' % (self.python, servicescript) > + > self.exitcodes = [0, 2] > if self.logfile is None and config.eventlog is not None: > for handler in config.eventlog.handler_factories: > @@ -158,11 +167,59 @@ > args = [opt, svalue] > return args > > + if WIN: > + def get_status(self): > + # get_status from zdaemon relies on *nix specific socket handling. > + # We just don't support getting the status and sending actions to > + # the control server on Windows. This could be extended to ask for > + # the status of the Windows service though > + self.zd_up = 0 > + self.zd_pid = 0 > + self.zd_status = None > + return > + > + def do_stop(self, arg): > + # Stop the Windows service > + program = "%s stop" % self.options.servicescript > + print program > + os.system(program) > + > + def do_restart(self, arg): > + # Restart the Windows service > + program = "%s restart" % self.options.servicescript > + print program > + os.system(program) > + > + # Add extra commands to install and remove the Windows service > + > + def do_install(self, arg): > + program = "%s install" % self.options.servicescript > + print program > + os.system(program) > + > + def help_install(self): > + print "install -- Installs Zope as a Windows service." > + > + def do_remove(self, arg): > + program = "%s remove" % self.options.servicescript > + print program > + os.system(program) > + > + def help_remove(self): > + print "remove -- Removes the Zope Windows service." > + > def do_start(self, arg): > # signal to Zope that it is being managed > - #(to indicate it's web-restartable) > + # (to indicate it's web-restartable) > os.putenv('ZMANAGED', '1') > - ZDCmd.do_start(self, arg) > + if WIN: > + # On Windows start the service, this fails with a reasonable > + # error message as long as the service is not installed > + program = "%s start" % self.options.servicescript > + print program > + os.system(program) > + else: > + ZDCmd.do_start(self, arg) > > def get_startup_cmd(self, python, more): > cmdline = ( '%s -c "from Zope2 import configure;' > @@ -179,12 +236,17 @@ > os.system(cmdline) > > def do_foreground(self, arg): > - self.options.program[1:1] = ["-X", "debug-mode=on"] > - try: > + if WIN: > + # Adding arguments to the program is not supported on Windows > + # and the runzope script doesn't put you in debug-mode either > ZDCmd.do_foreground(self, arg) > - finally: > - self.options.program.remove("-X") > - self.options.program.remove("debug-mode=on") > + else: > + self.options.program[1:1] = ["-X", "debug-mode=on"] > + try: > + ZDCmd.do_foreground(self, arg) > + finally: > + self.options.program.remove("-X") > + self.options.program.remove("debug-mode=on") > > def help_debug(self): > print "debug -- run the Zope debugger to inspect your database" > @@ -262,19 +324,23 @@ > args.insert(0, self.options.python) > > print 'Running tests via: %s' % ' '.join(args) > - pid = os.fork() > - if pid == 0: # child > - os.execv(self.options.python, args) > - > - # Parent process running (execv replaces process in child > - while True: > - try: > - os.waitpid(pid, 0) > - except (OSError, KeyboardInterrupt): > - continue > - else: > - break > + if WIN: > + # Windows process handling is quite different > + os.system(' '.join(args)) > + else: > + pid = os.fork() > + if pid == 0: # child > + os.execv(self.options.python, args) > > + # Parent process running (execv replaces process in child > + while True: > + try: > + os.waitpid(pid, 0) > + except (OSError, KeyboardInterrupt): > + continue > + else: > + break > + > def help_test(self): > print "test [args]+ -- run unit / functional tests." > print " See $ZOPE_HOME/bin/test.py --help for syntax." > @@ -317,7 +383,8 @@ > # If it is not reset, 'os.wait[pid]' can non-deterministically fail. > # Thus, use a way such that "SIGCHLD" is definitely reset in children. > #signal.signal(signal.SIGCHLD, signal.SIG_IGN) > - if os.uname()[0] != 'Darwin': > + if not WIN and os.uname()[0] != 'Darwin': > + # On Windows the os.uname method does not exist. > # On Mac OS X, setting up a signal handler causes waitpid to > # raise EINTR, which is not preventable via the Python signal > # handler API and can't be dealt with properly as we can't pass > > Copied: Zope/trunk/skel/bin/zopectl.bat.in (from rev 75039, Zope/trunk/skel/bin/runzope.bat.in) > =================================================================== > --- Zope/trunk/skel/bin/runzope.bat.in 2007-05-03 07:18:30 UTC (rev 75039) > +++ Zope/trunk/skel/bin/zopectl.bat.in 2007-05-03 18:35:20 UTC (rev 75066) > @@ -0,0 +1,8 @@ > +@set ZOPE_HOME=<<ZOPE_HOME>> > +@set INSTANCE_HOME=<<INSTANCE_HOME>> > +@set PYTHON=%ZOPE_HOME%\bin\python.exe > +@set SOFTWARE_HOME=%ZOPE_HOME%\lib\python > +@set CONFIG_FILE=%INSTANCE_HOME%\etc\zope.conf > +@set PYTHONPATH=%SOFTWARE_HOME% > +@set ZDCTL=%SOFTWARE_HOME%\Zope2\Startup\zopectl.py > +"%PYTHON%" "%ZDCTL%" -C "%CONFIG_FILE%" %1 %2 %3 %4 %5 %6 %7

3 3

Killer App for ZClasses
by Christopher Lozinski 04 May '07

04 May '07

Thank you very much for all the advice, and particularly for the list of problems with ZClasses. I had been thinking of jumping in and fixing some of those things. I am not quite sure where to start. What do I work on to benefit ZClasses, while taking care of my immediate business needs? I also must be mindful that I do not represent enough users to get my changes to the Zope core to be accepted and integrated into the product. Last night, I was wondering what should I do? Not only technically, what should I fix first, but also socially how should I proceed? Fortuitously, this morning, my associate Christopher Appell, who has been doing a brilliant job, calls me up and says: I want an application where we, and clients can track invoices. What I heard him say is: I need a very simple app. Just 1 ZClass, an invoice object. Not even subitems on the invoice. I want to create these ZClasses, I want a table of these ZClasses, I want to be able to say which role gets to create these objects, which role gets to see which fields, and which role gets to edit which fields. I would also like a search form with a ZCatalog, and I would like an edit/create form. All I want is to define the fields of the Zclass, and have the rest magically appear. I want the application to be built really quickly. Can you deliver by Monday? I thought, hey, I bet a million people need such a simple web app. Let us make it really easy to implement craigslist or better. Let me go ahead and create a ZClass product, and go ahead and distribute it. Lots of people would use it. Or at least enough to build up a critical mass. And then as some of those people go ahead and stretch the boundaries of the app, they will fix all of the ZClass problems we all know about. They will fix them for their own reasons, which is of course what drives open source. What do you think? Is this an effective way to operate on the social medium which is open source? Of course those who want to deprecate ZClasses will think this is a terrible terrible idea. I am fine with ZClasses being a separate product. I have a much richer deeper long-term vision of where this is going, but the longest road begins with a single step. Regards Chris

7 14

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 04 May '07

04 May '07

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 1310 Blamelist: jukart,mj BUILD FAILED: failed test sincerely, -The Buildbot

1 0