➜

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.

作者 Geraldo.Xexeo
收信人 Geraldo.Xexeo
日期 2010-07-18.01:51:32
SpamBayes Score 0.0011544424
Marked as misclassified 否
Message-id <1279417895.54.0.811089047738.issue9290@psf.upfronthosting.co.za>
In-reply-to
内容
The fact that in IDLE sys.stdin is a idlelib.rpc.RPCProxy  results in programs having different behavior in IDLE and in Command Line mode.

I noticed that when grading many students exercises in IDLE. Things like:

sys.stdin.readlines()

just don´t exists in IDLE, but are fully operational in Command Line mode.

In Command Line mode, sys.stdin is a file.

This is expected, as the manual (27.1) says that sys.stdin (and stdout and stderrr) are "File objects corresponding to the interpreter’s standard input"

There are also other "quirks".

I fell that is really strange that stdin has different behavior for the same program.
历史
日期 用户 动作 参数
2010-07-18 01:51:35Geraldo.Xexeo修改recipients: + Geraldo.Xexeo
2010-07-18 01:51:35Geraldo.Xexeo修改messageid: <1279417895.54.0.811089047738.issue9290@psf.upfronthosting.co.za>
2010-07-18 01:51:33Geraldo.Xexeo链接issue9290 messages
2010-07-18 01:51:32Geraldo.Xexeo创建