[issue33138] Improve standard error for uncopyable types

Serhiy Storchaka added the comment: Changed to "cannot pickle 'XXX' object" after discussing on Python-Dev: https://mail.python.org/pipermail/python-dev/2018-October/155599.html -- ___ Python tracker

[issue33138] Improve standard error for uncopyable types

Serhiy Storchaka added the comment: New changeset 0353b4eaaf451ad463ce7eb3074f6b62d332f401 by Serhiy Storchaka in branch 'master': bpo-33138: Change standard error message for non-pickleable and non-copyable types. (GH-6239)

[issue33138] Improve standard error for uncopyable types

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33138] Improve standard error for uncopyable types

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33138] Improve standard error for uncopyable types

Serhiy Storchaka added the comment: Does anybody have opinion about this issue? Is this option the best of possible? I'm going to merge the PR soon. -- assignee: -> serhiy.storchaka ___ Python tracker

[issue33138] Improve standard error for uncopyable types

Serhiy Storchaka added the comment: 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'

[issue33138] Improve standard error for uncopyable types

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +5978 stage: -> patch review ___ Python tracker ___

[issue33138] Improve standard error for uncopyable types

New submission from Serhiy Storchaka : Currently most extension types are not pickleable and copyable. The default error messages is "can't pickle XXX objects". This is confusing in case of copying because not all know that copying falls back to the pickle protocol