- Zope-Dev - Zope lists

Zope Tests: 5 OK
by Zope Tests Summarizer 11 Jul '08

11 Jul '08

Summary of messages to the zope-tests list. Period Thu Jul 10 11:00:00 2008 UTC to Fri Jul 11 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Jul 10 20:55:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009835.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 10 20:57:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009836.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 10 20:58:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009837.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 10 21:00:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009838.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 10 21:01:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009839.html

1 0

Proposal: add form support to zope.session.http.CookieClientIdManager
by Jim Fulton 10 Jul '08

10 Jul '08

As it's name implies, the CookieClientIdManager manages HTTP client ids using HTTP cookies. Recently, I've found it to be useful to be able to get a client id via form data. The reason is that flash programs don't send browser cookies. This bit me when trying to use the YUI uploader, http://developer.yahoo.com/yui/uploader/, which uses a flash program to select and upload files. I'm using session authentication and the only way I found to make it possible to upload files to protected pages was to pass the client id as form data. I have a custom client id manager that gets the id from form data as well as from a cookie. I propose to merge this with CookieClientIdManager. Any objections? Jim -- Jim Fulton Zope Corporation

3 3

PAULA: bringing Zope 3's authentication to Plone and beyond
by Florian Friesdorf 10 Jul '08

10 Jul '08

Hi *, within the scope of google summer of code I am integrating zope 3's PAU with Plone's PAS and further enable (non-AT) content objects as source for users and groups. All functionality is developed in pure zope3, the plone integration is happening in a separate packages. All documents describing the project, as well as links to the code can be found here: https://chaoflow.net/projects/gsoc2008/z3membrane-ldap The code is not very interesting right now, but now would be the time to take any influence on what will be created during the next month - I am planning to continue to work on the project after the SoC. I will keep you updated on major advancements of the code. regards florian

1 0

Zope3 installation on windows - how?
by Hermann Himmelbauer 10 Jul '08

10 Jul '08

Hi, I currently try to install Zope3-4.0c1 on a windows machine, without any success for now. What I need is an installation that includes basically all packages that are in the tarball into the python path. I tried the following: 1) Tarball: Here, install.py fails due to some compiler problems - it suggests to specify "-c mingw32", however, when I do so, install.py complains that it does not know this "-c mingw32" option. Something like "python install.py build_ext -cmingw32" works, it seems that all needed packages are correctly compiled. When I try a "python install.py install" afterwards, it once again complains that it needs mingw32. So I'm stuck. 2) I tried installing it via the descriptions given here: http://wiki.zope.org/zope3/Zope340c1 $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.1 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v This gives me some buildout error. 3) Next I tried the information from here: http://wiki.zope.org/zope3/MakingARelease svn co svn+ssh://svn.zope.org/repos/main/zope.release/branches/3.4 release-3.4 $ cd release-3.4 $ py24 bootstrap.py $ ./bin/buildout -N And there's once again this mingw32 problem. 4) Next, I tried zopeproject: $ easy_install zopeproject $ zopeproject HelloWorld First, zopeproject does not install the packages into the Python site-packages, moreover, there's once again the "mingw32" problem which I'm unable to solve. What can I do? Is there perhaps some precompiled Windows distribution for Zope-3.4 available? Or is there some trick to make things work with mingw32? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

2 2

zope.testing releases on PyPI
by Andreas Jung 10 Jul '08

10 Jul '08

Hi, the zope.testing releases on PyPI are apparently a bit weird. - zope.testing 3.5.1 has been the latest released version on PyPI last week - I created V 3.5.2 on Sunday. Phillip granted me access to the zope.testing package on PyPI in order to upload 3.5.2 (which worked) - I created V 3.5.3 yesterday morning. Uploading the egg was impossible because I had no longer rights (in fact permissions are currentl only granted to Jim and Fred Drake (not even Phillip) - search for "zope.testing" on PyPI leads me to version 3.0 instead of 3.5.1 Does anyone know what happened here? Andreas

4 3

Deprecation warnings from 2.11.0
by Chris Withers 10 Jul '08

10 Jul '08

Sidnei da Silva wrote: > On 6/25/08, Chris Withers <chris(a)simplistix.co.uk> wrote: >> Cool. Are the deprecation warning common to Zope 2.11 across all platforms? > > I don't see a reason why not, specially if coming from that module. Did we as a community really release a stable version that emits deprecation warnings?! :-( Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

zope.app.authentication broken!
by Roger Ineichen 10 Jul '08

10 Jul '08

hi I'm pretty sure the container changes are not compatible because of some bad __init__ methods in inherited classes in other packages. But that's not the fault of the refactoring that is correct as far as I can see. zope.app.authentication.groupfolder.py class GroupFolder(BTreeContainer): .... def __init__(self, prefix=u''): self.prefix=prefix super(BTreeContainer,self).__init__() ^^^^^^^^^^^^^^^^^^^^ The *super(BTreeContainer,self).__init__()* will not initialize the right thing here. right? What was the reason of calling: super(BTreeContainer,self).__init__() instead of: super(GroupFolder, self).__init__() btw, did someone run the tests with all packages that depend on zope.app.container? Regards Roger Ineichen _____________________________ END OF MESSAGE

2 3

Zope Tests: 5 OK
by Zope Tests Summarizer 10 Jul '08

10 Jul '08

Summary of messages to the zope-tests list. Period Wed Jul 9 11:00:00 2008 UTC to Thu Jul 10 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed Jul 9 21:00:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009830.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:02:21 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009831.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:03:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009832.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:05:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009833.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:06:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009834.html

1 0

Dangerous shutdown procedure behaviour
by Vincent Pelletier 09 Jul '08

09 Jul '08

Hi. I think I discovered a dangerous code behaviour at zope shutdown. I've had a strange problem on a site where persistent objects are created from data inserted in an SQL table. Upon object creation, SQL table is updated to mark the line as imported. Such import got triggered just before a shutdown. After restart and another import, documents were created twice. What I believe happened (but I could not find any hard evidence of it) is that Zope blindly exited while the working thread was runing, and in the worst possible method: tpc_finish. ZODB was already commited, but mysql was not. So mysql did a rollback on changes, and the lines were in a "ready to import" state. And imported again at next import attemp. Reading shutdown code, I discovered 2 distinct timeout mechanism (note: having just one is enough to trigger the problem): - Lifetime.py: iterating through asyncore sockets, it alerts servers that it will shut down soon. If they take the veto for too long, the veto is ignored and shutdown continues. Default timeout is 20 seconds, meaning there is at most one minute from the first shutdown notice to the effective process exit (taking all runing threads down). When invoking "zopectl stop", it's runing a "fast" shutdown, which means the timeout is shortened to 1 second, so total maximum sutdown time is 3 seconds. This timeout can be worked around by just writing blocking shutdown methods and not using the veto system. - zdaemon/zdrun.py: if the instance being shut down still responds after 10 seconds, it will be sent a SIGKILL. This cannot be worked around without changing code in zdrun.py or not executing it at all (no idea if there is any alternative). I could easily reproduce the problem by writing a simple connection mamager which calls time.wait(3600) in _finish method and defining a sortKey method to make it commit after another connection manager. I could not find a trace of any mechanism preventing commit from happening when a shutdown is in progress, and I don't think there should be any: considering that some storages might be accessed through a network, latency can become a problem, so tpc_finish can take time to complete, so just checking that there is no pending shutdown before entering this function would not solve the problem. I suggest removing all those timeouts. If a user wants a Zope to shutdown for a reason serious enough to send it a SIGKILL or causing immediate python thread termination, it's his responsibility. But I think regular shutdown mechanism must not do that. Also, the same problem can happen with "zopectl fg" since Zope does not go through any shutdown sequence as far as I can tell (it just dies). -- Vincent Pelletier

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 09 Jul '08

09 Jul '08

Summary of messages to the zope-tests list. Period Tue Jul 8 11:00:00 2008 UTC to Wed Jul 9 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Tue Jul 8 21:09:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009825.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:10:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009826.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:12:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009827.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:13:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009828.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:15:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009829.html

1 0