Message80543
| Author | mark.dickinson |
|---|---|
| Recipients | benjamin.peterson, fabioz, mark.dickinson, pitrou, vstinner |
| Date | 2009-01-25.22:00:37 |
| SpamBayes Score | 4.534769e-08 |
| Marked as misclassified | No |
| Message-id | <1232920838.76.0.6394216998.issue4705@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> So the question is whether it is really useful to enforce unbuffered > stdin with the '-u' option (or your example is simply too borderline). Hard to say. It seems at least possible that there are Python users for whom stdin being unbuffered (with -u) matters, so if there's any reasonable way of avoiding changing this it should probably be considered. Though I have to admit that I'm not one of those users (I don't think I've *ever* used the -u option outside of testing...). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-01-25 22:00:38 | mark.dickinson | set | recipients: + mark.dickinson, pitrou, vstinner, fabioz, benjamin.peterson |
| 2009-01-25 22:00:38 | mark.dickinson | set | messageid: <1232920838.76.0.6394216998.issue4705@psf.upfronthosting.co.za> |
| 2009-01-25 22:00:38 | mark.dickinson | link | issue4705 messages |
| 2009-01-25 22:00:37 | mark.dickinson | create | |