[issue2582] Unpickling of range objects fail in Py3k
Alexandre Vassalotti [EMAIL PROTECTED] added the comment: Fixed in r64059 for Python 3.0 Fixed in r64056 and r64057 for Python 2.6 -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
Alexandre Vassalotti [EMAIL PROTECTED] added the comment: Fixed in r64056 and r64057 for Python 2.6 Oops, I meant r64057 and r64058. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
Alexandre Vassalotti [EMAIL PROTECTED] added the comment: Weird. I wonder why it succeeds to pickle to range object at all. It seems the __reduce_ex__ method emits bogus value. r.__reduce_ex__(2) (function __newobj__ at 0xb7bfdc94, (class 'range',), None, None, None) Anyway, that is easy to fix when you know the trick. So, here is the fix. -- assignee: - alexandre.vassalotti keywords: +patch nosy: +alexandre.vassalotti Added file: http://bugs.python.org/file10530/fix_range_pickling.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
Alexandre Vassalotti [EMAIL PROTECTED] added the comment: Oh, here is a slightly more efficient version. Added file: http://bugs.python.org/file10531/fix_range_pickling-2.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
Alexandre Vassalotti [EMAIL PROTECTED] added the comment: xrange() in Python 2.x is also affected by this bug. So, here is the fix. -- versions: +Python 2.5, Python 2.6 Added file: http://bugs.python.org/file10532/fix_xrange_pickling.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- priority: - critical __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2582] Unpickling of range objects fail in Py3k
New submission from Anand B Pillai [EMAIL PROTECTED]: Unpickling of range objects is throwing an exception in Python 3.0 -- components: Interpreter Core, Library (Lib) files: bugdemo.py messages: 65157 nosy: pythonhacker severity: normal status: open title: Unpickling of range objects fail in Py3k versions: Python 3.0 Added file: http://bugs.python.org/file9981/bugdemo.py __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2582 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com