-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
bpo-37627: Initialize IDLE Custom Run dialog with previous entries #14870
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.
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
bpo-37627: Initialize IDLE Custom Run dialog with previous entries #14870
Conversation
85b1f40 to
cf1aee9
Compare
|
Please be very careful with bpo numbers when submitting. To fix, one must go the wrong issue and remove the misplaced link, then change the number in the title and 3 places in the comment. (This should be in the devguide.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tracker issue and this PR are about two different subjects: the Run menu and persisting user command line entries. I will want these split, but can't now say what change to make.
So don't do anything immediately.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
Can we get this done before 3.8 goes final? The user testing indicated that both sub-issues were problematic. That said, I'm happy to have the feature at all. It was a nice improvment for developing command-line scripts using IDLE. |
|
I want to split the menu change, for which I have an alternative proposal, from the argument persistence, which I was going to merge by tomorrow. I did not realize that 'delete file' meant 'delete the whole file' as opposed to the changes to the file, so I have to patch this PR or write another. There does not seem to be a way in the UI to revert a deletion. |
|
Yeah, Siregar it is |
|
Thanks @nsiregar for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
|
@terryjreedy: Please replace |
…ythonGH-14870) Repeat the command line arguments most recently entered before so the user can edit them. (cherry picked from commit 35b87e6) Co-authored-by: Ngalim Siregar <ngalim.siregar@gmail.com>
|
GH-14881 is a backport of this pull request to the 3.8 branch. |
…ythonGH-14870) Repeat the command line arguments most recently entered before so the user can edit them. (cherry picked from commit 35b87e6) Co-authored-by: Ngalim Siregar <ngalim.siregar@gmail.com>
|
GH-14882 is a backport of this pull request to the 3.7 branch. |
|
Thanks @nsiregar for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
|
I'm having trouble backporting to |
|
Thanks @nsiregar for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
…ythonGH-14870) Repeat the command line arguments most recently entered before so the user can edit them. (cherry picked from commit 35b87e6) Co-authored-by: Ngalim Siregar <ngalim.siregar@gmail.com>
|
GH-14893 is a backport of this pull request to the 3.8 branch. |
|
@Mariatta I have re-added 'needs backport to 3.8' twice with no response at all after several minutes |
|
The last one seemed to work |
…ython#14870) Repeat the command line arguments most recently entered before so the user can edit them.
…ython#14870) Repeat the command line arguments most recently entered before so the user can edit them.
…ython#14870) Repeat the command line arguments most recently entered before so the user can edit them.
Repeat the command line arguments most recently entered before so the user can edit them.
https://bugs.python.org/issue37627