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 | vstinner |
|---|---|
| Recipients | benjamin.peterson, pitrou, serhiy.storchaka, stutzbach, vstinner |
| Date | 2017年06月19日.11:46:51 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1497872811.97.0.283816661203.issue30404@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Oh, I like https://github.com/python/cpython/pull/1667/ "If write_through is True, calls to write() are guaranteed not to be buffered: any data written on the TextIOWrapper object is immediately handled to its underlying binary buffer." I didn't know write_through. It seems like it was introduced in Python 3.7: bpo-30526, commit 3c2817b6884a5fcf792197203f3c26b157210607. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年06月19日 11:46:52 | vstinner | set | recipients: + vstinner, pitrou, benjamin.peterson, stutzbach, serhiy.storchaka |
| 2017年06月19日 11:46:51 | vstinner | set | messageid: <1497872811.97.0.283816661203.issue30404@psf.upfronthosting.co.za> |
| 2017年06月19日 11:46:51 | vstinner | link | issue30404 messages |
| 2017年06月19日 11:46:51 | vstinner | create | |