➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xzy3
Recipients xzy3
Date 2020-07-10.13:58:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1594389522.96.0.51886326593.issue41270@roundup.psfhosted.org>
In-reply-to
Content 
_TemporaryFileWrapper does not proxy __next__ to the underlying file object. There was a discussion on the mailing list in 2016 mentioning this, however it seems it was dropped without a consensus. Biopython encountered this issue (referenced below) and we agree it violates our assumptions about how the NamedTemporaryFile should work. I think it would be fairly trivial to fix by just returning `self.file.readline()`

mailing list thread: https://mail.python.org/pipermail/python-list/2016-July/862590.html

biopython discussion: https://github.com/biopython/biopython/pull/3031
History
Date User Action Args
2020-07-10 13:58:43xzy3setrecipients: + xzy3
2020-07-10 13:58:42xzy3setmessageid: <1594389522.96.0.51886326593.issue41270@roundup.psfhosted.org>
2020-07-10 13:58:42xzy3linkissue41270 messages
2020-07-10 13:58:42xzy3create