pickle vs cPickle: error is not raised at unpickle
pickle vs cPickle: error is not raised at unpickle / windows vs linux (!) (repost)
Tim Peters tim.one at comcast.netSun Jun 8 21:12:16 EDT 2003
- Previous message (by thread): pickle vs cPickle: error is not raised at unpickle / windows vs linux (!) (repost)
- Next message (by thread): pickle vs cPickle: error is not raised at unpickle / windows vs linux (!) (repost)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Irmen de Jong] > windows vs linux (!) (repost) > > > Irmen de Jong wrote: > >> I'm experiencing a problem with pickle vs cPickle. [...] >> - python 2.2.2 *and* 2.3b under linux tell me everything is fine > > Scratch that. I did something wrong, Python2.2.2 and 2.3b on > Linux act the same as on Windows. > > Still, my first question remains: > >> 1) with the unmodified code, why doesn't cPickle raise an error when >> the unpickling gets in an endless loop ? This is why bug reports don't belong on comp.lang.python: the context is lost, and I don't have time to go searching for it. When you don't get a reply to a repeated question about dubious behavior, it's probably because nobody reading c.l.py knows the answer. In this case, there are maybe two people on Earth who understand all the pickle changes going into 2.3, and Guido (the one who knows best) rarely has time to read c.l.py anymore. So, if you think this is an important question, please gather all the pieces and open a single coherent bug report on SourceForge. Or, if it's an idle question, feel encouraged to keep replying to yourself about it on c.l.py <wink>.
- Previous message (by thread): pickle vs cPickle: error is not raised at unpickle / windows vs linux (!) (repost)
- Next message (by thread): pickle vs cPickle: error is not raised at unpickle / windows vs linux (!) (repost)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list