classification
Title: cPickle defect with tuples and different from pickle output
Type: behavior Stage:
Components: Library (Lib) Versions: Python 2.5
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, jelle
Priority: normal Keywords:

Created on 2009-04-28 14:06 by jelle, last changed 2009-05-25 02:23 by collinwinter. This issue is now closed.

Messages (2)
msg86741 - (view) Author: Jelle (jelle) Date: 2009-04-28 14:06
Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
[GCC 4.3.2] on linux2

>>> print cPickle.dumps(('a','b')) == cPickle.dumps(('a', str('b')))
False
>>> print pickle.dumps(('a','b')) == pickle.dumps(('a', str('b')))
True
>>> print pickle.dumps(('a','b')) == cPickle.dumps(('a', str('b')))
False
>>> print pickle.dumps(('a','b')) == cPickle.dumps(('a', 'b'))
False
msg86756 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-04-28 17:55
As long as the different pickle outputs unpickle to the same objects
(which they do, since they only differ in pushing objects to the memo),
I can't see why this would be a bug.
History
Date User Action Args
2009-05-25 02:23:03collinwintersetstatus: pending -> closed
2009-04-28 17:55:16georg.brandlsetstatus: open -> pending

nosy: + georg.brandl
messages: + msg86756

resolution: wont fix
2009-04-28 14:07:02jellesettype: behavior
2009-04-28 14:06:03jellecreate