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 serhiy.storchaka
Recipients Dhiraj_Mishra, martin.panter, mbussonn, python-dev, serhiy.storchaka, socketpair, takluyver
Date 2016-04-23.20:59:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461445179.22.0.223233119015.issue26039@psf.upfronthosting.co.za>
In-reply-to
Content
test_write_after_read was added in issue14099. It doesn't test intended behavior, it tests existing behavior just in case to not change it unintentionally. It is desirable to preserve it, but if there is no simple way, may be we can change it.
History
Date User Action Args
2016-04-23 20:59:39serhiy.storchakasetrecipients: + serhiy.storchaka, socketpair, python-dev, takluyver, martin.panter, mbussonn, Dhiraj_Mishra
2016-04-23 20:59:39serhiy.storchakasetmessageid: <1461445179.22.0.223233119015.issue26039@psf.upfronthosting.co.za>
2016-04-23 20:59:39serhiy.storchakalinkissue26039 messages
2016-04-23 20:59:39serhiy.storchakacreate