New submission from Xiang Gao :
Related: https://bugs.python.org/issue1820
On issue 1820, a bunch of improvements was made on PyStructSequence to make it
behave like a namedtuple. These improvements are not ported to Python 2, which
makes it a trouble to write python 2-3 compatible code
Xiang Gao added the comment:
Hi Eric,
Thanks for your valuable information and fast reply. You understand the problem
exactly correct: initially pytorch had codes like `isinstance(x, tuple)` and
lots of `PyTuple_Check`, but when we start to change the return type from tuple
to structseq
