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 random832
Recipients random832
Date 2020-01-17.04:23:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579234995.29.0.127298904142.issue39365@roundup.psfhosted.org>
In-reply-to
Content
Currently this fails with a (misleading in the case of SEEK_END) "Can't do nonzero cur-relative seeks" error, but there's no conceptual reason it shouldn't be possible.

The offset should simply be taken as a character offset, without any pretense that the "file" represents bytes in some Unicode encoding. This is already done for SEEK_START and tell, and has not caused any problems.
History
Date User Action Args
2020-01-17 04:23:15random832setrecipients: + random832
2020-01-17 04:23:15random832setmessageid: <1579234995.29.0.127298904142.issue39365@roundup.psfhosted.org>
2020-01-17 04:23:15random832linkissue39365 messages
2020-01-17 04:23:15random832create