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 vitaly.krug
Recipients christian.heimes, pitrou, serhiy.storchaka, vitaly.krug
Date 2018-03-24.17:37:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALVBdqtf5sY0qjG7mmEXOGYWJLemWYmg5TaFvPogY3dQ2TP5og@mail.gmail.com>
In-reply-to <1521901713.95.0.467229070634.issue33023@psf.upfronthosting.co.za>
Content
Thank you, I'll consider myself having been warned :)

On Sat, Mar 24, 2018, 7:28 AM Christian Heimes <report@bugs.python.org>
wrote:

>
> Christian Heimes <lists@cheimes.de> added the comment:
>
> Serhiy,
> I don't understand what you are trying to tell me. "cannot serialize '%s'
> object" is used all over the interpreter, e.g. io, pickle, etree, and more.
> I feel it's the standard message.
>
> Vitaly,
> A lot of objects can't be copied. It's the general case for all kinds of
> objects that hold operating system resources (files, sockets) or wrap
> external C libraries (bz2, lzma, sqlite, ssl). We generally don't document
> that an object cannot be pickled, serialized, or copied. If documentation
> doesn't state that an object is copy-able or doesn't provide a dedicated
> copy method, than it can't be copied.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33023>
> _______________________________________
>
History
Date User Action Args
2018-03-24 17:37:41vitaly.krugsetrecipients: + vitaly.krug, pitrou, christian.heimes, serhiy.storchaka
2018-03-24 17:37:41vitaly.kruglinkissue33023 messages
2018-03-24 17:37:41vitaly.krugcreate