[issue1724366] cPickle module doesn't work with universal line endings

2020-05-31 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- nosy: +serhiy.storchaka resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker

[issue1724366] cPickle module doesn't work with universal line endings

2019-03-15 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1724366] cPickle module doesn't work with universal line endings

2015-03-01 Thread Mark Lawrence
Mark Lawrence added the comment: msg185431 from #616013 states Three years later, I don't think anyone is interested in documenting the outdated cPickle. so I believe this should suffer the same fate. -- ___ Python tracker rep...@bugs.python.org

[issue1724366] cPickle module doesn't work with universal line endings

2014-06-12 Thread Mark Lawrence
Mark Lawrence added the comment: Can this be closed as issue616013 was? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1724366 ___

[issue1724366] cPickle module doesn't work with universal line endings

2010-07-15 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: This does not look like a valid bug to me. OP does not show that pickle files are different on different systems, he mangles pickle file with unix2dos instead. This would certainly produce an invalid pickle because

[issue1724366] cPickle module doesn't work with universal line endings

2010-07-15 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Antoine, to answer your question about universal newlines in pickle in msg87622. The pickle.py docsstrings in 2.7+ contain the following text (amongst others): The optional protocol argument tells the pickler to use the

[issue1724366] cPickle module doesn't work with universal line endings

2010-07-15 Thread Alexander Belopolsky
Alexander Belopolsky belopol...@users.sourceforge.net added the comment: The pickle.py docsstrings in 2.7+ contain the following text (amongst others): .. Protocol 0 is the only protocol that can be written to a file opened in text mode and read back successfully. Hmm,

[issue1724366] cPickle module doesn't work with universal line endings

2009-05-12 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: Confirmed in trunk and py3k. -- components: +IO nosy: +ajaksu2, benjamin.peterson, pitrou stage: - test needed type: - behavior versions: +Python 2.6, Python 3.1 -Python 2.4 Added file:

[issue1724366] cPickle module doesn't work with universal line endings

2009-05-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Why would use a file in universal line endings mode for saving/loading pickles? Pickles are binary data (even if version 0 pickles happens to be human-readable), so you should open the files in binary mode (either rb or wb). -- versions:

[issue1724366] cPickle module doesn't work with universal line endings

2009-05-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Also, I don't understand how you confirmed this bug under py3k. Text files under py3k forbid bytes input, which is what pickle produces: pickle.dump([], sys.stdout) Traceback (most recent call last): File stdin, line 1, in module File

[issue1724366] cPickle module doesn't work with universal line endings

2008-05-03 Thread Ronald Oussoren
Changes by Ronald Oussoren [EMAIL PROTECTED]: -- assignee: jackjansen - _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1724366 _ ___ Python-bugs-list mailing