Has anyone got any ideas how I'd go about inestigating this?
You could try to figure out in what state Zope is when it
blocks. Does is consumes time? Maybe, you can use a debugger
to determine in what state the various threads are.
This may give us a hint where the block is established.
Chris Withers writes:
Dieter Maurer wrote:
Chris Withers writes:
urllib Client block Zope
That would suggest a bug in Python's socket implementation:
its "makefile().read" method would not release the global
interpreter lock.
Do you think this is
Dieter Maurer wrote:
Chris Withers writes:
urllib Client block Zope
That would suggest a bug in Python's socket implementation:
its "makefile().read" method would not release the global
interpreter lock.
Do you think this is likely? If so, where would I go to report it,
Hi,
Both urllib and Client.py can be used to get stuff from other sites via HTTP and
do useful stuff with it, right?
Well, I was doing this and I think I've found what could be a 'real bad
problem'.
It appears that both of the above block while getting stuff from the remote
site. Worse than
Chris Withers writes:
urllib Client block Zope
That would suggest a bug in Python's socket implementation:
its "makefile().read" method would not release the global
interpreter lock.
Dieter
___
Zope-Dev maillist - [EMAIL PROTECTED]
