[issue6213] Incremental encoder incompatibility between 2.x and py3k

[Walter Dörwald]

Walter Dörwald <walter at livinglogic.de> added the comment:

AFAICR the difference is: 2.x may return any object in getstate(), but
py3k must return a (buffered input, integer) tuple. Simply moving py3ks
getstate/setstate implementation over to 2.x might do the trick.

----------

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