Serhiy Storchaka added the comment:
If issue17897 fixes this bug (I'm not absolutely sure), perhaps it should be
backported to 3.3.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18073
Changes by Alexandre Vassalotti alexan...@peadrop.com:
--
assignee: - alexandre.vassalotti
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18073
Serhiy Storchaka added the comment:
Seems as the patch for issue17897 fixes this case.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18073
___
Dylan Radcliffe added the comment:
What I see in gdb is that that read is occurring due to the unpickling thread
reading peeking ahead in the stream due to buffered io being used.
#0 0x77bcbcbd in read () from /lib/x86_64-linux-gnu/libpthread.so.0
#1 0x0061f521 in
Antoine Pitrou added the comment:
For the record, this is one of the things that the framing proposal in pickle
protocol 4 (pep 3154 - http://www.python.org/dev/peps/pep-3154/#framing) is
able to address.
--
___
Python tracker
New submission from Julien Muchembled:
I use pickle over sockets to make 2 processes communicate and I experience
hangs when the resulting pickle message is exactly 4097 bytes.
Attached file is a small script reproducing the issue, trying a few values
around 4096. It runs on both Python 2.7
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +alexandre.vassalotti, pitrou, serhiy.storchaka
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18073
___
