Georg Brandl ge...@python.org added the comment:
Okay, as the original submitter I withdraw this request.
--
resolution: - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2572
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
Recommend that this be closed with no action taken. It is an important
step for Py3.x that old style classes be left behind and that no mention
of them occur in the 3.x docs. Let's not carry 2.x with us into the 3.x
world.
Jeroen Ruigrok van der Werven asmo...@in-nomine.org added the comment:
We want to document that old-style classes get converted into new-style
classes and that in general this goes without problems, except for some
corner cases such as containing a __slots__ directive? Or did I miss
anything
Georg Brandl ge...@python.org added the comment:
Sounds like this is the best that we without intimate pickle knowledge
can do :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2572
___
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Alexandre, would you mind fixing up the docs?
--
nosy: +benjamin.peterson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2572
__
New submission from Georg Brandl [EMAIL PROTECTED]:
Can 3.0 unpickle pickled old-style classes? Which pickling methods are
supported? Etc.
--
assignee: alexandre.vassalotti
components: Documentation
messages: 65098
nosy: alexandre.vassalotti, georg.brandl
severity: normal
status: open
Alexandre Vassalotti [EMAIL PROTECTED] added the comment:
Python 3.0 shouldn't have any problem unpickling old-style classes.
However, they will be unpickled as new-style classes. Therefore, there
might be a few corner-cases that might cause some problems. For example,
if an old-style class
