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 hagen
Recipients alexandre.vassalotti, hagen
Date 2008-08-27.13:03:23
SpamBayes Score 0.000184894
Marked as misclassified No
Message-id <>
Well, this is obviously caused by renaming "__builtin__" to "builtins"
and the fact that set (as well as frozenset) doesn't have its own opcode
and therefore gets looked up in "builtins". The problem therefore
extends to all builtin objects without opcode special casing (e.g.
object, slice, property, ...) I'm afraid that means we have to pickle
"builtins" as "__builtin__" for backwards compatibility in protocols <= 2.

But aside from that, wouldn't it be more consistent to have opcodes for
set/frozenset in protocol 3?
Date User Action Args
2008-08-27 13:03:25hagensetrecipients: + hagen, alexandre.vassalotti
2008-08-27 13:03:24hagensetmessageid: <>
2008-08-27 13:03:24hagenlinkissue3675 messages
2008-08-27 13:03:23hagencreate