[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2011-02-17 Thread Ron Adam
Changes by Ron Adam ron_a...@users.sourceforge.net: -- nosy: +ron_adam ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2571 ___ ___ Python-bugs-list

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-11-14 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- status: closed - open type: - feature request versions: +Python 3.2 -Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2571 ___

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-11-13 Thread Michael Hoffman
Changes by Michael Hoffman qq9jsuv...@snkmail.com: -- nosy: +hoffman ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2571 ___ ___ Python-bugs-list

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-10-18 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: You could say my question was half-academic. I read your closing message and thought “this feature request has been closed because of the version, not really rejected”, so I asked about reopening. On a second level, it appears from your

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-10-07 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: Since 'we' can reopen any closed issue, I will try to answer what I think you might be asking. I closed this because of Daniel's suggestion coupled with the Richard disclaiming further interest and neither Raghuram nor any new responder

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-10-07 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Can we reopen this as a feature request for 3.2? -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2571 ___

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2010-04-29 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: Too late for new 2.7 features. -- nosy: +tjreedy resolution: - out of date status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2571

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2009-04-28 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: Changing into a RFE: automatically set use_rawinput when 'stdin' is not None. Will be closed unless someone voices interest. -- components: +Library (Lib) -Extension Modules keywords: +easy priority: - low stage: - test needed status:

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-06-19 Thread Raghuram Devarakonda
Raghuram Devarakonda [EMAIL PROTECTED] added the comment: On Wed, Jun 18, 2008 at 9:28 PM, Richard King [EMAIL PROTECTED] wrote: Richard King [EMAIL PROTECTED] added the comment: There were some other things I wanted too so I just made my own cmd.py. Yes. Lot of people seem to use their own

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-06-18 Thread Raghuram Devarakonda
Raghuram Devarakonda [EMAIL PROTECTED] added the comment: Richard, I see the following very clearly mentioned in the doc: If you want a given stdin to be used, make sure to set the instance’s use_rawinput attribute to False, otherwise stdin will be ignored. Even though this seems like

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-06-18 Thread Richard King
Richard King [EMAIL PROTECTED] added the comment: There were some other things I wanted too so I just made my own cmd.py. -Rick Raghuram Devarakonda wrote: Raghuram Devarakonda [EMAIL PROTECTED] added the comment: Richard, I see the following very clearly mentioned in the doc: If you want

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-04-08 Thread Richard King
Richard King [EMAIL PROTECTED] added the comment: (this is really 2 mails because my home email address was not registered so they were rejected at first) Right - I wasn't too clear. The module stashes stdin, whether from sys or passed in, in self.stdin. When it reads input it uses a flag

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-04-07 Thread Richard King
New submission from Richard King [EMAIL PROTECTED]: The module global value use_rawinput is initialized to 1 but not reset when stdin is replaced with a passed-in value. -- components: Extension Modules messages: 65094 nosy: rickbking severity: normal status: open title: cmd.py always

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-04-07 Thread Daniel Diniz
Daniel Diniz [EMAIL PROTECTED] added the comment: I don't think it should stop using raw_input just because you changed stdin, as you can change it to something that will work with raw_input. Consider: import sys sys.stdin = open(/dev/tty) raw_input() a 'a' You can tie it to any object (e.g.

[issue2571] cmd.py always uses raw_input, even when another stdin is specified

2008-04-07 Thread Raghuram Devarakonda
Raghuram Devarakonda [EMAIL PROTECTED] added the comment: The doc for cmd at http://docs.python.org/dev/library/cmd.html#module-cmd says: Instances of Cmd subclasses have some public instance variables: . . . Cmd.use_rawinput¶ A flag, defaulting to true. If true, cmdloop() uses raw_input()