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月12日 22:35 by MLModel, last changed 2022年04月11日 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| PyShell-3.1.diff | MLModel, 2009年02月12日 22:35 | mods to enable IDLE's loading startup file on restart | ||
| unnamed | MLModel, 2009年03月09日 14:50 | |||
| Messages (4) | |||
|---|---|---|---|
| msg81832 - (view) | Author: Mitchell Model (MLModel) | Date: 2009年02月12日 22:35 | |
The main thing the patch does is: modify the subprocess restart procedure so that it reloads whatever file, if any, was loaded when IDLE first started and looked for IDLESTARTUP then PYTHONSTARTUP environment variables. In addition: a -q option is added for starting IDLE on the command line to mean "quiet", as with Emacs, e.g., to suppress loading of IDLESTARTUP or PYTHONSTARTUP The former effect of -s would now be the default, which is desirable so double-clicking an IDLE icon to start it will cause the startup file to run. -s is changed to take an argument that is an alternate startup file to use I am a bit concerned about changing -s to have a different meaning. Perhaps it's better to leave -s as an option that is simplhy superfluous and use a different letter for the alternate startup. |
|||
| msg83360 - (view) | Author: Martin v. Löwis (loewis) * (Python committer) | Date: 2009年03月09日 06:58 | |
How does that differ from issue5233? If this is a straight-forward port, no additional issue is needed. Even if there are differences, please attach the patch to the other issue. |
|||
| msg83387 - (view) | Author: Mitchell Model (MLModel) | Date: 2009年03月09日 14:50 | |
Same changes to the code, but starting from a different base. I had assumed since IDLE/PyShell.py was different in Python 2 and 3 that I needed to submit separate issues each with its own patch. I've attached the 3.1 patch to issue5233, so you can close issue5234. (Though doesn't it still make sense to have separate issues since it my happen that it gets integrated into Python 3 but not Python 2, and then what would the status of the issue be?) -- -- --- Mitchell |
|||
| msg83398 - (view) | Author: Guilherme Polo (gpolo) * (Python committer) | Date: 2009年03月09日 19:21 | |
Closing in favor of 5233, I see the fix being applied to both 2.7 and 3.1 if accepted. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:56:45 | admin | set | github: 49484 |
| 2009年03月09日 19:21:38 | gpolo | set | status: open -> closed nosy: + gpolo messages: + msg83398 superseder: IDLE: exec IDLESTARTUP/PYTHONSTARTUP on restart resolution: duplicate |
| 2009年03月09日 14:50:59 | MLModel | set | files:
+ unnamed messages: + msg83387 |
| 2009年03月09日 06:58:15 | loewis | set | nosy:
+ loewis messages: + msg83360 |
| 2009年02月12日 22:40:55 | rhettinger | set | assignee: kbk nosy: + kbk |
| 2009年02月12日 22:35:28 | MLModel | create | |