- Zope-Dev - Zope lists

Zope Installers for Windows: ready for testing
by Sidnei da Silva 18 Apr '07

18 Apr '07

It's that time again... fire up your VMs and do some testing. Let's get those up on the website ASAP! http://files.enfoldsystems.com/Zope-2.10.3-Final-7151.exe http://files.enfoldsystems.com/Zope-2.9.7-Final-7151.exe -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

2 2

Zope Tests: 5 OK
by Zope Tests Summarizer 18 Apr '07

18 Apr '07

Summary of messages to the zope-tests list. Period Tue Apr 17 12:00:00 2007 UTC to Wed Apr 18 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 Apr 17 20:54:06 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007598.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Apr 17 20:55:37 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007599.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Apr 17 20:57:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007600.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Apr 17 20:58:39 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007601.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Apr 17 21:00:10 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007602.html

1 0

The problem with ZClasses is a symptom of two problems with Zope 2
by Christopher Lozinski 17 Apr '07

17 Apr '07

Why are there such problems with ZClasses, when they were written by intelligent people? I think I now know the answer to that. I am pretty sure that the permissions mechanism makes ZClasses have propertysheets, so that access to variables can share a permission. I am pretty sure that the Products structure makes ZClasses have their create methods at the same level as the ZClass, rather than 1 level below the Z Class in a class methods folder. So what do I have to do to fix ZClasses? What I am thinking of doing is taking the newest release of Zope 2, and tossing out permissions, and tossing out the Products piece, and then putting in place what I need to do fast through the web development. I will put in place a simpler permissions system. I will miss Formulator and Localizer, because they are tied in with the existing permissions mechanisms. But they should migrate over easily. I will probably break everything else in sight in the process. Maybe I need to keep the Products piece, and put in place NewProducts or something like that. But I will have a very nice upgrade path for ZClass based applications. And why do I keep getting flamed? There is some world view that does not like my world view. Why are permissions so broken in Zope2. They are way too complex. Why has no one released Zope 2 with cleaner permissions? Because it breaks everything? Thank you to all the people who recommended that I use CMF or Python Classes, or Zope 3. None of those are quite what I want and need. ZClasses is close to what I need, I just need to fix it. Regards Christopher Lozinski

2 1

Zope Tests: 5 OK
by Zope Tests Summarizer 17 Apr '07

17 Apr '07

Summary of messages to the zope-tests list. Period Mon Apr 16 12:00:00 2007 UTC to Tue Apr 17 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 Apr 16 20:52:54 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007593.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Apr 16 20:54:25 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007594.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Apr 16 20:55:57 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007595.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Apr 16 20:57:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007596.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Apr 16 20:58:59 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007597.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 16 Apr '07

16 Apr '07

Summary of messages to the zope-tests list. Period Sun Apr 15 12:00:00 2007 UTC to Mon Apr 16 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 Apr 15 20:48:49 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007588.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Apr 15 20:50:19 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007589.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Apr 15 20:51:49 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007590.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Apr 15 20:53:19 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007591.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Apr 15 20:54:49 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007592.html

1 0

Zope Tests:
by Zope Tests Summarizer 15 Apr '07

15 Apr '07

Summary of messages to the zope-tests list. Period Sat Apr 14 12:00:00 2007 UTC to Sun Apr 15 12:00:00 2007 UTC. There were no messages.

1 0

Zope Tests:
by Zope Tests Summarizer 14 Apr '07

14 Apr '07

Summary of messages to the zope-tests list. Period Fri Apr 13 12:00:00 2007 UTC to Sat Apr 14 12:00:00 2007 UTC. There were no messages.

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 13 Apr '07

13 Apr '07

Summary of messages to the zope-tests list. Period Thu Apr 12 12:00:00 2007 UTC to Fri Apr 13 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: Thu Apr 12 20:49:58 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007583.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Apr 12 20:51:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007584.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Apr 12 20:52:58 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007585.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Apr 12 20:54:28 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007586.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Apr 12 20:55:58 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-April/007587.html

1 0

Sessions and long requests = conflicts? Mcdutils?
by Maciej Wisniowski 12 Apr '07

12 Apr '07

Hi Currently I have some problems with our application (Zope2.8.4) and with Conflict Errors in sessions. In general if we have few concurrent requests that are running sometimes for 3-4 minutes (and they're touching session inside) I get a lot of conflict errors with Inceraser, OOBTree, Length2 etc. These are errors like: serial starded with xxx serial currently commited xxxx Of course I know that it is best to move such long processes to something external with Async, lovely.Remotetask or built in Oracle jobs, but so far I have to deal with this state of our application (as I'm not the author ot this but rather something like an zope admin/supporter for this app). I think that ConflictErrors are caused because of sessions implementation, especially: timeslices, "current" bucket etc. as written in Transience/HowTransienceWorks.stx. Changing session_resolution_seconds to big value helps here. By default we had session_resolution_seconds set to 300. I wonder how this happens. If I have two requests that at the beginning modify it's sessions like: session.set('aa', 1), and then call long running ZSQLMethods then (if meanwhile timeslice has changed because of too short session_resolution_seconds): - first request that finishes finds that there is new 'current' bucket and moves it's session object and second request's session object to new 'current' bucket and commits this - second request finishes and finds that it's session object is not the same as it was at the beginning (because it was moved to 'current' bucket)?? Anybody can say if I'm right here? I also tried Faster product to manage sessions but this behaves in a similiar way (I mean causes conflict errors in such situation). I found 'mcdutils' too. Tres Seaver said on zope-dev (a long time ago) that it is supposed to have no conflict errors: http://mail.zope.org/pipermail/zope-dev/2006-May/027555.html Mcdutils: http://agendaless.com/Members/tseaver/software/mcdutils There is only 0.1 version. What is it's current state? Seems to be dead? Can I take a look at this or is this better to not even touch that? -- Maciej Wisniowski

4 8

unit tests
by Miles 12 Apr '07

12 Apr '07

Hi, I am running a set of unit tests for a custom product nightly via a buildbot installation, via bin/zopectl test -s Products.MyProduct in zope 2.9. Sorry in advance that this looks complicated - my query is actually pretty straightforward! Recently, I introduced a bug in the __init__.py of the product, which caused the product installation to fail in zope. The following was written to stdout: 2007-04-12 10:05:34 ERROR Zope Couldn't install CMFMyProduct Traceback (most recent call last): File "/usr/local/Zope-2.9.5/lib/python/OFS/Application.py", line 783, in install_product initmethod(context) File "/home/buildslave/buildslaves/astrodon/build/Zope-2.9.5/Products/CMFMyProduct/__init__.py", line 227, in initialize context.registerClass(MyModule.MyClass, NameError: global name 'MyModule' is not defined The trivial error was that MyModule was not imported earlier in __init__.py However, having logged this, the testrunner proceeded to run all my tests correctly, and so the buildbot reported a pass. I expected the testrunner to bomb out on encountering this error, but it didn't - however if I start zope with zopectl fg, the bug I introduced causes it to fail to start. I'm a bit concerned that there was a false test pass. Is there a way to stop the testrunner in this case, in the same way as running in fg mode? Thanks, Miles

3 2