You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following behavior should be documented but it is not:
If the user has a .Idle.py file IDLE will run it when it starts up. This
is independent of running IDLESTARTUP or PYTHONSTARTUP when the -s
switch is given. It is run by Tk.readprofile as called from Tk.__init__.
The "Idle" comes from the name passed to TK() when PyShell.py creates
its Tk root. In fact, not only is it independent, but it works
differently: any imports done in .Idle.py go into Tk's name space,
whereas IDLESTARTUP/PYTHONSTARTUP is exec'd and imports go into the
interpreter's namespace.
Note that the 'I' in '.Idle.py' is really uppercase, which will matter
on case-sensitive platforms.
Here's a simple patch that documents the different startup files. It is
missing a good use case for .Idle.py but I'd be happy to add that if
someone can give me one.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: