gh-69708: IDLE "Save As" warnings by ZackerySpytz · Pull Request #17051 · python/cpython
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 34.4k
Open
ZackerySpytz wants to merge 1 commit intopython:mainfrom
Open
gh-69708: IDLE "Save As" warnings#17051
ZackerySpytz wants to merge 1 commit intopython:mainfrom
gh-69708: IDLE "Save As" warnings#17051
ZackerySpytz wants to merge 1 commit intopython:mainfrom
Conversation
Copy link Copy Markdown
Contributor
Give a warning when attempting to save a file that shadows a module
in the standard library.
Give a warning when attempting to save a file that shadows a module in the standard library.
ZackerySpytz
requested a review
from terryjreedy
as a code owner
the-knights-who-say-ni
added
the
CLA signed
label
bedevere-bot
added
the
awaiting review
label
ezio-melotti
removed
the
CLA signed
label
hauntsaninja
changed the title
bpo-25522: IDLE "Save As" warnings
gh-69708: IDLE "Save As" warnings
Copy link Copy Markdown
Member
serhiy-storchaka
commented
Dec 26, 2023
serhiy-storchaka commented
Dec 26, 2023- The warning should only be emitted if the file extension matches Python source extensions. IDLE allows to edit other text files, they do not conflict with modules.
- The warning should only be emitted for saving a new file. If file already exists, then the user already saved it and asked the question.
- There should be more reliable way to determine if the name conflicts with an existing module. For example using
importlib.util.find_spec().
terryjreedy
mentioned this pull request
Copy link Copy Markdown
github-actions
bot
commented
Apr 7, 2026
github-actions bot commented
Apr 7, 2026This PR is stale because it has been open for 30 days with no activity.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment