➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients alexandre.vassalotti, christian.heimes, pitrou, serhiy.storchaka
Date 2018-06-07.07:04:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528355086.97.0.592728768989.issue33138@psf.upfronthosting.co.za>
In-reply-to
Content 
Current error messages for different classes:

   "can't pickle XXX objects" (default)
   "Cannot serialize XXX object" (socket, BZ2Compressor, BZ2Decompressor)
   "can not serialize a 'XXX' object" (buffered files in _pyio)
   "cannot serialize 'XXX' object" (FileIO, TextWrapperIO, WinConsoleIO, buffered files in _io, LZMACompressor, LZMADecompressor)

Yest one error message is proposed by PR 6099 in issue33023 for SSLContext:

   "cannot serialize {} object"

PR 6239 replaces them with unified

   "cannot serialize 'XXX' object"

which already is used in some extension classes. This is the most popular error message except the default error message. I'm not sure this is the best error message. "can't"/"Cannot"/"cannot"/"can not", using an article and quotes -- what is better?
History
Date User Action Args
2018-06-07 07:04:47serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, christian.heimes, alexandre.vassalotti
2018-06-07 07:04:46serhiy.storchakasetmessageid: <1528355086.97.0.592728768989.issue33138@psf.upfronthosting.co.za>
2018-06-07 07:04:46serhiy.storchakalinkissue33138 messages
2018-06-07 07:04:46serhiy.storchakacreate