| View previous topic :: View next topic |
| Author |
Message |
Ikopar
Joined: 26 May 2006 Posts: 168
|
| You prefer the DOS-box over IDLE? Why? |
| |
|
|
|
|
Koplaf
Joined: 28 May 2006 Posts: 130
|
| { and [ are obvious sending control signals/characters to the prompt. I have no idea why, but googling "square bracket dos control signal" or similar might tell you. |
| |
|
|
Ikopar
Joined: 26 May 2006 Posts: 168
| |
Kopilman
Joined: 25 May 2006 Posts: 162
|
| My keyboard / regular "cmd" prompts / cygwin work just fine... it's *only* when I run interactive python... |
| |
|
|
Ikopar
Joined: 26 May 2006 Posts: 168
|
Kopilman, Also, what do you get by running this:
Python -Ec "import sys; print sys.stdin.encoding" & mode con cp |
| |
|
|
Kopilman
Joined: 25 May 2006 Posts: 162
|
Ikopar, this works, output in pastebin => python -Ec "import sys; print sys.stdin.encoding" & mode con cp
this "works" but doesn't display anything, si... => import msvcrt; print msvcrt.getch() |
| |
|
|
Ikopar
Joined: 26 May 2006 Posts: 168
|
At the prompt, type ‘command’; at the new prompt, type ‘python -’
But getch() works for the other keys, yes? |
| |
|
|
Kopilman
Joined: 25 May 2006 Posts: 162
|
look at this:
>>> msvcrt.getch()
'['
>>>
Hadn't understood what you were telling me, sorry
So, getch() works just fine for the characters that give me trouble otherwise |
| |
|
|
Ikopar
Joined: 26 May 2006 Posts: 168
|
| Try: ‘python con’ |
| |
|
|
Kopilman
Joined: 25 May 2006 Posts: 162
|
That works
I.e. [ works
This kinda helps me, but I'd love to know wtf is going wrong :-) |
| |
|
|
|