Message162802
| Author |
r.david.murray |
| Recipients |
jaraco, r.david.murray |
| Date |
2012-06-14.16:07:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1339690054.4.0.585187548431.issue15068@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
Frankly I'm surprised it works at all, since fileinput.input() will by default read from stdin, and stdin is in turn being read by the python prompt.
I just checked 2.5 on linux, and the same situation exists there (two ^Ds are required to end the input()). I suspect we'll find the explanation in the interaction between the default behavior of fileinput.input() and the interactive prompt. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012-06-14 16:07:34 | r.david.murray | set | recipients:
+ r.david.murray, jaraco |
| 2012-06-14 16:07:34 | r.david.murray | set | messageid: <1339690054.4.0.585187548431.issue15068@psf.upfronthosting.co.za> |
| 2012-06-14 16:07:33 | r.david.murray | link | issue15068 messages |
| 2012-06-14 16:07:33 | r.david.murray | create | |
|