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 | pitrou |
|---|---|
| Recipients | jcea, pitrou, vstinner |
| Date | 2011年06月05日.11:25:41 |
| SpamBayes Score | 8.96715e-05 |
| Marked as misclassified | No |
| Message-id | <1307273139.3540.1.camel@localhost.localdomain> |
| In-reply-to | <1306756651.54.0.607962084751.issue12213@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> My patch tries to fix interlaced read-write by always calling flush(), Why do you need to call flush()? Can't you read from the buffer? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年06月05日 11:25:42 | pitrou | set | recipients: + pitrou, jcea, vstinner |
| 2011年06月05日 11:25:41 | pitrou | link | issue12213 messages |
| 2011年06月05日 11:25:41 | pitrou | create | |