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

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

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

Changes by Florent Xicluna florent.xicl...@gmail.com: -- nosy: +flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8323 ___ ___ Python-bugs-list

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

Richard Oudkerk shibt...@gmail.com 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

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

sbt shibt...@gmail.com 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