[issue8323] buffer objects are picklable but result is not unpicklable

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

While buffer is only used in Python 2.x, there is a similar issue in 3.x with 
memoryview.

The patch for issue22995 fixes this issue.

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8323] buffer objects are picklable but result is not unpicklable

[Florent Xicluna]

Changes by Florent Xicluna :


--
nosy: +flox

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8323] buffer objects are picklable but result is not unpicklable

[Richard Oudkerk]

Richard Oudkerk  added the comment:

It seems the real issue here is that buffer objects are picklable (depending on 
protocol) but the resulting string is not unpicklable.

There are probably lots of other examples where this happens: for instance 
Exception subclasses which do not set self.args correctly (see Issue #1692335).

buffer is only used in Python 2.x.  Python 2.7 is in bugfix mode, so this issue 
will not change now.

I will close this issue as "won't fix".

--
resolution:  -> wont fix
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue8323] buffer objects are picklable but result is not unpicklable

[sbt]

sbt  added the comment:

Buffer objects *are* picklable with protocol 2 (but not with earlier 
protocols).  Unfortunately, the result is not unpicklable.  

This is not a problem with multiprocessing.  (buffer seems to inherit 
__reduce__ and __reduce_ex__ from object.)

Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) 
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import cPickle
>>> cPickle.dumps(buffer("hello"), cPickle.HIGHEST_PROTOCOL)
'\x80\x02c__builtin__\nbuffer\nq\x01)\x81q\x02.'
>>> cPickle.loads(_)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: buffer() takes at least 1 argument (0 given)

--
nosy: +sbt
title: multiprocessing.Queue ignores pickle restrictions in .put() -> buffer 
objects are picklable but result is not unpicklable

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com