http://codytaylor.org/2009/05/what-happened-to-my-terminal.html From Cody Taylor. Thu, 13 Oct 2011 06:41:44 -0700 http://wordpress.org/?v=2.8.4 hourly 1 http://codytaylor.org/2009/05/what-happened-to-my-terminal.html/comment-page-1#comment-2449 Matt Sun, 31 May 2009 03:38:00 +0000 http://codytaylor.org/?p=14063#comment-2449 .pyc files are indeed compiled byte code rather than the .py source file(I believe, me and python had a fight many years ago and haven't spoken in a while). What actually causes the corrupt display is the fact that the character sequence representing ^n was sent to the display, putting your terminal into a mode that uses the 8 bit IBM PC Exctended Character Set rather than what it was set to previously (whether UTF-8 style or 7 bit ASCII). The side effect of this is that the incorrect characters are displayed. This can typically be fixed by typing: reset Or by using ^o. .pyc files are indeed compiled byte code rather than the .py source file(I believe, me and python had a fight many years ago and haven’t spoken in a while). What actually causes the corrupt display is the fact that the character sequence representing ^n was sent to the display, putting your terminal into a mode that uses the 8 bit IBM PC Exctended Character Set rather than what it was set to previously (whether UTF-8 style or 7 bit ASCII). The side effect of this is that the incorrect characters are displayed. This can typically be fixed by typing:
reset
Or by using ^o.

]]>