[Zope-dev] Re: [Zope-DB] Thread in ZODB
You can't associate thread or locks as *persistent* attributes. Use
_v_someattribute
instead.
-aj
P.S. and please no crosspostings
--On Samstag, 10. April 2004 10:33 Uhr +0200 Andre Meyer
[EMAIL PROTECTED] wrote:
Hi Zopers
Here is a nice challenge, I hope:
I have a multi-threaded Python application that I want to link to Zope.
The idea is to provide a Web interface for viewing and editing the state
of multiple threads running in Python. On thread should be associated
with Zope and act as the door between the ZServer and the other threads.
Unfortunately, I do not manage to create a reference to a thread in the
Zope product's main class because the ZODB refuses to add it.
This is the error message when trying to instantiate the product:
Site Error
An error was encountered while publishing this resource.
Error Type: UnpickleableError
Error Value: Cannot pickle type 'thread.lock' objects
And this is the code where it goes wrong:
class Zpyse(SimpleFolder):
meta_type = Zpyse
manage_options = (
{'label':'Edit', 'action':'manage_main'},
{'label':'View', 'action':'index_html'}
)
index_html = PageTemplateFile('zpt/index_html', globals())
def manage_editZpyse(self, title, REQUEST=None):
Method to edit Zpyse instances.
self.title = title
if REQUEST is not None:
return self.index_html(self, REQUEST)
def __init__(self, id, title):
# Sender/Receiver Test
print 'init Zpyse'
ams = spyse.getAMS()
* self.za = ams.createThread('ZopeThread', 'ZopeThread', globals())
qa = ams.createThread('Receiver', 'ReceiverThread', globals())
sa = ams.createThread('Sender', 'SenderThread', globals())
* only this goes wrong, the other threads are created (without self.).
Is there anybody with a good idea about how to handle this?
thanks a lot in advance
Andre
___
Zope-Dev maillist - [EMAIL PROTECTED]
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 )
[Zope-dev] Re: [Zope-DB] Thread in ZODB
Thanks, the hint of Sandor with adding the thread as an attribute to the
module instead of the class worked well for me.
sorry for cross-posting
kind regards
Andre
Andreas Jung wrote:
You can't associate thread or locks as *persistent* attributes. Use
_v_someattribute
instead.
-aj
P.S. and please no crosspostings
--On Samstag, 10. April 2004 10:33 Uhr +0200 Andre Meyer
[EMAIL PROTECTED] wrote:
Hi Zopers
Here is a nice challenge, I hope:
I have a multi-threaded Python application that I want to link to Zope.
The idea is to provide a Web interface for viewing and editing the state
of multiple threads running in Python. On thread should be associated
with Zope and act as the door between the ZServer and the other
threads.
Unfortunately, I do not manage to create a reference to a thread in the
Zope product's main class because the ZODB refuses to add it.
This is the error message when trying to instantiate the product:
Site Error
An error was encountered while publishing this resource.
Error Type: UnpickleableError
Error Value: Cannot pickle type 'thread.lock' objects
And this is the code where it goes wrong:
class Zpyse(SimpleFolder):
meta_type = Zpyse
manage_options = (
{'label':'Edit', 'action':'manage_main'},
{'label':'View', 'action':'index_html'}
)
index_html = PageTemplateFile('zpt/index_html', globals())
def manage_editZpyse(self, title, REQUEST=None):
Method to edit Zpyse instances.
self.title = title
if REQUEST is not None:
return self.index_html(self, REQUEST)
def __init__(self, id, title):
# Sender/Receiver Test
print 'init Zpyse'
ams = spyse.getAMS()
* self.za = ams.createThread('ZopeThread', 'ZopeThread',
globals())
qa = ams.createThread('Receiver', 'ReceiverThread', globals())
sa = ams.createThread('Sender', 'SenderThread', globals())
* only this goes wrong, the other threads are created (without self.).
Is there anybody with a good idea about how to handle this?
thanks a lot in advance
Andre
--
Dr. Andre P. Meyerhttp://home.hccnet.nl/a.meyer/
TNO FEL Command Control and Simulation, http://www.fel.tno.nl/div2/
Delft Cooperation on Intelligent Systems, http://www.decis.nl/
___
Zope-Dev maillist - [EMAIL PROTECTED]
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 )
[Zope-dev] Proposal: Move to subversion for source code control of the Zope and ZODB projects
I propose to move from CVS to subversion for the Zope and ZODB projects; http://dev.zope.org/Zope3/MovingSCMToSubversion Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS. Comments are welcome here, and in the Wiki. I propose to make this a topic of discussion at the upcoming Zope commnity IRC chat: http://mail.zope.org/pipermail/zope-announce/2004-April/001409.html Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
[Zope-dev] Re: Proposal: Move to subversion for source code control of the Zope and ZODB projects
Jim Fulton wrote: I propose to move from CVS to subversion for the Zope and ZODB projects; http://dev.zope.org/Zope3/MovingSCMToSubversion Initially, I propose to move just the repository heads. Maintenamce branches (e.g. Zope 2.6 and Zope 2.7) will remain in CVS. Finally ... :) +1 Christian ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Proposal: Move to subversion for source code control of
Jim Fulton wrote: I propose to move from CVS to subversion for the Zope and ZODB projects; http://dev.zope.org/Zope3/MovingSCMToSubversion Not adding to the repository my voice should not carry much weight, but I absolutely love subversion here on Windows. -- hilsen/regards Max M, Denmark http://www.mxm.dk/ IT's Mad Science ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Proposal: Move to subversion for source code control of the Zope and ZODB projects
Jim Fulton wrote: I propose to move from CVS to subversion for the Zope and ZODB projects; http://dev.zope.org/Zope3/MovingSCMToSubversion No complaints from me. I do wonder though... one thing I've noticed about ZC's CVS usage in the past is that you folks never export your code for releases. Indeed, the 2.7.0 source release wasn't even checked out with -P so there's a lot of goofy-looking empty directories in the tarball. A common idiom through a great deal of the code is: __version__='$Revision: 1.201 $'[11:-2] Now... thats a cute hack, but its also a silly waste of time. If releases were exported with -kv, it wouldn't be necessary. If you're going to switch to subversion, could I humbly suggest that you actually follow a release process that obviates the need for that kinda stuff? Changing revision control systems is a perfect time to do that kind of thing as everybody is the mode of learning new a process. -- Jamie Heilman http://audible.transient.net/~jamie/ Paranoia is a disease unto itself, and may I add, the person standing next to you may not be who they appear to be, so take precaution. -Sathington Willoughby ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
