Incompatibility.py
Colin J. Williams
cjw at connection.com
Tue Jul 27 09:01:23 EDT 1999
More information about the Python-list mailing list
Tue Jul 27 09:01:23 EDT 1999
- Previous message (by thread): Incompatibility.py
- Next message (by thread): Tkinter bug ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark, I enter IDLE, from the W95 Desktop, with the Target set to IDLE.py and the Start In set to the working directory. Similarly, for PythonWin, the Target is PythonWin.exe. The results are as reported below. At one time one could set breakpoints in IDLE, this capability was lost in some later download. I applaud the Tim Peters suggestion in this thread. It would also be nice if the IDLE line number were displayed, as is done in PythonWin. Thanks, Colin W. Mark Hammond wrote: > Colin J. Williams wrote in message <379C8BB3.12D50F27 at connection.com>... > > >IDLE returns: The name is: Incompatibility > > Not for IDLE 0.5 it doesnt. Are you sure you are not using "Import Script". > IDLE definately does this, as Python uses the "if __name__=='__main__':" > idiom extensively - and IDLE would be useless for running scripts if it did > as you describe. > > The behaviour you describe sounds like you are simply confusing "Run Script" > with "Import Script". > > Mark.
- Previous message (by thread): Incompatibility.py
- Next message (by thread): Tkinter bug ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list