Help with Tkinter and MacPython
Russell E. Owen
owen at astrono.junkwashington.emu
Wed May 30 13:05:36 EDT 2001
In article <3B148D6D.37789E0E at spiritone.com>,
Josh English <english at spiritone.com> wrote:
>"Russell E. Owen" wrote:
>
>> Also, there are at least two standard gotchas, both well documented in
>> the ReadMe:
>> - All versions of MacPython require you to drop a script on
>> PythonInterpreter. Never try to run Tk scripts in Python IDE!
>
>I haven't found that in the Read Me files, but it works. Thanks.
I'm very glad that did it! I looked around and you're right, the info
isn't in the Readme. I found it in the "Relnotes" file in the "Relnotes"
folder. I have appended the "known limitations" section from that file
(which also contains other useful information). While I'm at it, a big
"thank you" to Jack Jansen and the others who make MacPython happen.
-- Russell
Known problems
--------------
This list is probably incomplete, more problems may be listed on the
MacPython homepage,
http://www.cwi.nl/~jack/macpython.html.
- Tkinter does not work under Carbon.
- The IDE and Tkinter do not work together. Run tkinter programs under
PythonInterpreter.
- Tkinter file events do not work, unless you have opened the file
through Tcl (but then
you cannot access it from Python).
- Aliases may not work in sys.path entries.
- Under Carbon on OS9 only you may occasionally see a spurious
KeyboardInterrupt. I have absolutely
no clue as to what is causing this.
- PythonInterpreter used interactively will eat a lot of processor
cycles. You should use
PythonIDE for interactive work and PythonInterpreter for scripts only.
This is especially
true under OSX.
More information about the Python-list
mailing list