➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2009-02-15 23:41 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| idlestartdoc.patch | bmiller, 2009-03-10 17:49 | |||
| Messages (3) | |||
|---|---|---|---|
| msg82186 - (view) | Author: Mitchell Model (MLModel) | Date: 2009-02-15 23:41 | |
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. |
|||
| msg83442 - (view) | Author: Brad Miller (bmiller) | Date: 2009-03-10 17:49 | |
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. |
|||
| msg83646 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2009-03-15 21:52 | |
Thanks, edited a bit and committed in r70395. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:45 | admin | set | github: 49526 |
| 2009-03-15 21:52:01 | georg.brandl | set | status: open -> closed messages: + msg83646 resolution: fixed |
| 2009-03-10 17:49:39 | bmiller | set | files:
+ idlestartdoc.patch nosy: + bmiller messages: + msg83442 keywords: + patch |
| 2009-02-15 23:41:56 | MLModel | create | |