Message258578
| Author | martin.panter |
|---|---|
| Recipients | Daniel.Gonzalez, bhuvan, eric.araujo, ezio.melotti, ggenellina, jaraco, martin.panter, mdomingues, serhiy.storchaka, taleinat |
| Date | 2016-01-19.10:36:30 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1453199791.34.0.51921898995.issue1927@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The way I see it, input() is mainly geared for prompting to stdout, and it is just one aspect that strangely uses stderr: * Documentation says stdout * Stdout is checked if it is a terminal and not redirected * Gnu Readline is configured for stdout * The fallback for non-terminals uses stdout Arguments for using stderr: * Consistency with Unix shell * Consistency with the Python interactive interpreter prompt Maybe it is more ideal to use stderr (I have no idea). But I think that would be a more drastic change. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-01-19 10:36:31 | martin.panter | set | recipients: + martin.panter, jaraco, ggenellina, taleinat, ezio.melotti, eric.araujo, mdomingues, serhiy.storchaka, Daniel.Gonzalez, bhuvan |
| 2016-01-19 10:36:31 | martin.panter | set | messageid: <1453199791.34.0.51921898995.issue1927@psf.upfronthosting.co.za> |
| 2016-01-19 10:36:31 | martin.panter | link | issue1927 messages |
| 2016-01-19 10:36:30 | martin.panter | create | |