New submission from Ben Bass benb...@codedstructure.net:
The new SIGINT behaviour of pdb.Pdb prevents use of pdb within a non-main
thread without explicitly setting nosigint=True. Specifically the 'continue'
command causes a traceback as follows:
{{{
...
File
/Library/Frameworks
Changes by Ben Bass benb...@codedstructure.net:
--
title: Default nosigint optionto pdb.Pdb() prevents use in non-main thread -
Default nosigint option to pdb.Pdb() prevents use in non-main thread
___
Python tracker rep...@bugs.python.org
http
Ben Bass benpaulb...@googlemail.com added the comment:
Perhaps this should be addressed separately, but subprocess.CalledProcessError
is subject to this problem (can't be unpickled) (it has separate returncode and
cmd attributes, but no args).
It's straightforward to conform user-defined
Ben Bass benpaulb...@googlemail.com added the comment:
Same applies to collections.deque, which seems closely related (being another
collections class). Can this get addressed here or should I open another issue?
(just been pprinting defaultdict(deque) objects, which clearly fails
Ben Bass benpaulb...@googlemail.com added the comment:
'connectionless' is from how I see it as an analogy with UDP (vs TCP);
why not just use a deque is primarily about having the same API - a
client (getter) of the queue shouldn't know or care whether it is a
'lossy' queue or a normal queue
New submission from Ben Bass benpaulb...@googlemail.com:
Many applications would benefit from 'connectionless' queues, i.e. they
don't want to care whether anything is reading from the other end.
Using current queue module classes this is not practical, because there
is a choice between
New submission from Ben Bass:
To quickly open a PyDoc browser, I want to be able to run the following:
python -m pydoc -g
This works fine on Python2.4, but fails on 2.5(.1), with following
traceback (tested on both WinXP and Solaris 8, same result):
Traceback (most recent call last):
File c
Ben Bass added the comment:
I've just bumped into this issue. In my opinion the finish() method
should only do anything if wfile is not empty, i.e:
temp = self.wfile.getvalue()
if temp:
self.socket.sendto(temp, self.client_address)
--
nosy: +bpb
Ben Bass added the comment:
Main issue here (as I see it) is that StreamRequestHandler and
DatagramRequestHandler should behave in the same way. This is not the
case in Python 2.5.1 for the case where the handle method does not
respond to the request socket (e.g. in my case it is forwarding
