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 martin.panter
Recipients Jonathan Kamens, Paolo Veglia, benjamin.peterson, jmadden, marcjofre, martin.panter, pitrou, pje, serhiy.storchaka, stutzbach, tarek
Date 2016-06-02.23:29:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464910142.89.0.202340851873.issue24291@psf.upfronthosting.co.za>
In-reply-to
Content
I prefer your first solution because it seems to fit in better with how things were intended.

I can add in handling of partial writes with a deprecation warning when I get a chance. I guess the documentation would be something like “Since 3.5.2, partial writes are also handled, but this is deprecated.”
History
Date User Action Args
2016-06-02 23:29:02martin.pantersetrecipients: + martin.panter, pje, pitrou, benjamin.peterson, tarek, stutzbach, serhiy.storchaka, jmadden, Jonathan Kamens, marcjofre, Paolo Veglia
2016-06-02 23:29:02martin.pantersetmessageid: <1464910142.89.0.202340851873.issue24291@psf.upfronthosting.co.za>
2016-06-02 23:29:02martin.panterlinkissue24291 messages
2016-06-02 23:29:02martin.pantercreate