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 | chris.jerdonek |
|---|---|
| Recipients | chris.jerdonek, ncoghlan |
| Date | 2012年08月07日.07:30:01 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1344324604.0.0.525136882575.issue15571@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The fact that the Python implementation doesn't look at write_through doesn't necessarily mean that it's not respected. It could always write through. Indeed, it looks like this is the case and was discussed at one point: http://bugs.python.org/issue12591#msg141006 Also, it appears that there is a test in both cases (the test class is subclassed twice), though I could be wrong: http://hg.python.org/cpython/file/0eeffeadaa1e/Lib/test/test_io.py#l2453 In any case, this could probably at least use a code comment. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年08月07日 07:30:05 | chris.jerdonek | set | recipients: + chris.jerdonek, ncoghlan |
| 2012年08月07日 07:30:03 | chris.jerdonek | set | messageid: <1344324604.0.0.525136882575.issue15571@psf.upfronthosting.co.za> |
| 2012年08月07日 07:30:03 | chris.jerdonek | link | issue15571 messages |
| 2012年08月07日 07:30:01 | chris.jerdonek | create | |