Hagen Fürstenau <[EMAIL PROTECTED]> added the comment: 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? _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3675> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
