Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enhance 3.1 IDLE to exec IDLESTARTUP/PYTHONSTARTUP on restart #49484

Closed
MLModel mannequin opened this issue Feb 12, 2009 · 4 comments
Closed

Enhance 3.1 IDLE to exec IDLESTARTUP/PYTHONSTARTUP on restart #49484

MLModel mannequin opened this issue Feb 12, 2009 · 4 comments
Assignees
@kbkaiser
Labels
topic-IDLE type-bug An unexpected behavior, bug, or error

Comments

@MLModel
Copy link
Mannequin

MLModel mannequin commented Feb 12, 2009

BPO 5234
Nosy @loewis, @kbkaiser, @MLModel
Superseder
  • bpo-5233: IDLE: exec IDLESTARTUP/PYTHONSTARTUP on restart
    		•
    Files
  • PyShell-3.1.diff: mods to enable IDLE's loading startup file on restart
  • unnamed
    		•

    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:

    assignee = 'https://github.com/kbkaiser'
closed_at = <Date 2009-03-09.19:21:38.876>
created_at = <Date 2009-02-12.22:35:28.763>
labels = ['expert-IDLE', 'type-bug']
title = 'Enhance 3.1 IDLE to exec IDLESTARTUP/PYTHONSTARTUP on restart'
updated_at = <Date 2009-03-09.19:21:38.874>
user = 'https://github.com/MLModel'

    bugs.python.org fields:

    activity = <Date 2009-03-09.19:21:38.874>
actor = 'gpolo'
assignee = 'kbk'
closed = True
closed_date = <Date 2009-03-09.19:21:38.876>
closer = 'gpolo'
components = ['IDLE']
creation = <Date 2009-02-12.22:35:28.763>
creator = 'MLModel'
dependencies = []
files = ['13059', '13287']
hgrepos = []
issue_num = 5234
keywords = ['patch']
message_count = 4.0
messages = ['81832', '83360', '83387', '83398']
nosy_count = 4.0
nosy_names = ['loewis', 'kbk', 'gpolo', 'MLModel']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '5233'
type = 'behavior'
url = 'https://bugs.python.org/issue5234'
versions = ['Python 3.1']
    @MLModel
    Copy link
    Mannequin Author

    MLModel mannequin commented Feb 12, 2009

    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.

    @MLModel MLModel mannequin added topic-IDLE type-bug An unexpected behavior, bug, or error labels Feb 12, 2009
    @loewis
    Copy link
    Mannequin

    loewis mannequin commented Mar 9, 2009

    How does that differ from bpo-5233? 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.

    @MLModel
    Copy link
    Mannequin Author

    MLModel mannequin commented Mar 9, 2009

    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 bpo-5233, so you can close bpo-5234.
    (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

    @gpolo
    Copy link
    Mannequin

    gpolo mannequin commented Mar 9, 2009

    Closing in favor of 5233, I see the fix being applied to both 2.7 and
    3.1 if accepted.

    @gpolo gpolo mannequin closed this as completed Mar 9, 2009
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees

    @kbkaiser kbkaiser

    Labels
    topic-IDLE type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    1 participant
    @kbkaiser