|
Thank god, finally someone cares this! Thank
you, Bruce! Let me explain that a little more. By "interactive session", I mean the session I get when I execute 'python' in a gnome shell. That works OK. I did not mean the one comes with IDLE, which is not OK. Some days later after the last email I reported this, I found that there is nothing to do with hitting RETURN after ")" in a function call and it was not the 'File->Print Window' gets my keyboard back. Actually, it seems that every time I finish typing the ")" of 'somefunction(whatever)', I mean in IDLE shell, I lose focus to the IDLE shell window. The window does looks like it is on focus, but keyboard seems focusing on something else (the indicator still blanking). Then all I have to do is to click anywhere on the IDLE menu bar or to just simply switch windows back and forth with ALT+TAB to re-focus on the IDLE window, and boom, I get the keyboard back. One more RETURN afterwards gets the 'somefunction(whatever)' finally called. And later on, if I type 'anotherfunction(with_or_without_arg)', as soon as I finish typing the ")", I lose my keyboard reaction from IDLE again! Really strange, isn't it?! Could it be a gnome problem? I've tried several other editors, and this is only happening to IDLE. I asked this strange question on some forums like ubuntuforums.org, by far I get no answer/solution but suggestions to use other python editors like Geany. As I said, I'm a beginner of Python and I think there must be some reason that IDLE comes with python on MS Windows. I'd really like to stick on IDLE to make it more 'native' way. So please, can some one help on this? If any other details are needed to help to address this problem, please drop me an email. Thanks! Sincerely, 叶 峰|Crow Yeh(Ye Feng) Bruce Sherwood wrote: I'm also running Ubuntu 8 with Python 2.5, and I don't see any of the misbehavior that you see.However, it's possible that I don't understand your comment, "Python interactive session works OK as expected. It seems that only IDLE doesn't like RETURN to be hit after the tailing "()" of functions." First you say it works OK, then you say it doesn't work OK. I have no idea what's wrong on your machine, but in the IDLE shell window I can definitely execute the function calls that you are unable to execute. Bruce Sherwood 叶 峰|Crow Yeh(Ye Feng) wrote: |
_______________________________________________ IDLE-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/idle-dev
