[issue3338] cPickle segfault with deep recursion

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

> Well, it's definitely a bug, or inconsistency, if you like, between
> cPickle and pickle.

There is clearly a problem with cPickle stack consumption and a new bug has been
opened for this in #3640.

What I don't agree with is your argument that pickle and cPickle should have the
same recursion limits - it's just "foolish consistency" to ask for identical
behaviour on such a low-level and implementation-dependent issue.

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3338>
_______________________________________