You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/avassalotti'closed_at=<Date2008-06-10.04:05:51.017>created_at=<Date2008-04-08.12:39:01.162>labels= ['interpreter-core', 'library']
title='Unpickling of range objects fail in Py3k'updated_at=<Date2008-06-10.04:06:54.902>user='https://bugs.python.org/pythonhacker'
Activity
pythonhacker commentedon Apr 8, 2008
Unpickling of range objects is throwing an exception in Python 3.0
avassalotti commentedon Jun 5, 2008
Weird. I wonder why it succeeds to pickle to range object at all. It
seems the __reduce_ex__ method emits bogus value.
Anyway, that is easy to fix when you know the trick. So, here is the fix.
avassalotti commentedon Jun 5, 2008
Oh, here is a slightly more efficient version.
avassalotti commentedon Jun 5, 2008
xrange() in Python 2.x is also affected by this bug. So, here is the fix.
avassalotti commentedon Jun 10, 2008
Fixed in r64059 for Python 3.0
Fixed in r64056 and r64057 for Python 2.6
avassalotti commentedon Jun 10, 2008
Oops, I meant r64057 and r64058.