[issue17296] Cannot unpickle classes derived from 'Exception'
Andreas Hausmann added the comment:
That is correct.
Under 2.4 and 3.3 it should show neither the line EXCEPTION ## EXCEPTION nor
the following line TypeError: ('__init__() takes at least 2 arguments.
That means, that in version 2.4 and 3.3 that unpickling problem doesn't exist.
In version 2.4 I tested it myself; exactly, there is no problem. In version 3.3
I simply take your word, that the bug is fixed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17296
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17296] Cannot unpickle classes derived from 'Exception'
Andreas Hausmann added the comment: A backport to 2.7 would be in the interest of the Zope community (I dare say ;)), at least in ours. In our project, after having migrated to Zope 2.13/Python2.7 we found this bug and now we are quite worried what else might happen with our huge pickled database. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17296 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17296] Cannot unpickle classes derived from 'Exception'
New submission from Andreas Hausmann:
When pickling/unpickling a class that derives from the builtin class Exception,
unpickling results in a
TypeError: ('__init__() takes at least 2 arguments (1 given)', class
'__main__.TestException', ())
A standard exception like ValueError can be pickled/unpickled without any
problem.
This was observed for versions 2.7.3 and 3.2.3. for both pickle and cPickle.
A script (cpickle) that shows that behavior is included.
This is related (but I do not quite understand how) to the closed Issue1692335.
--
components: Interpreter Core
files: bug_cpickle.py
messages: 182960
nosy: Andreas.Hausmann, alexandre.vassalotti, belopolsky, benjamin.peterson,
bpb, brett.cannon, ehuss, facundobatista, fmitha, georg.brandl, gvanrossum,
haypo, jafo, jarpa, jason.coombs, kylev, loewis, lukasz.langa, nnorwitz,
pitrou, python-dev, sbt, taleinat, tseaver, zbysz, zseil
priority: normal
severity: normal
status: open
title: Cannot unpickle classes derived from 'Exception'
type: behavior
versions: Python 2.7, Python 3.2
Added file: http://bugs.python.org/file29234/bug_cpickle.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17296
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17296] Cannot unpickle classes derived from 'Exception'
Andreas Hausmann added the comment: I have not tried in 3.3. I have no running installation of 3.3. I need a solution for 2.7 for a Zope project that was just ported to 2.7. My test for Python3 was halfheartedly on my standard Python3 installation (3.2) after reading Issue1692335. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17296 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
