I have issues with Python IDLE 3.xx under windows

Python Help
1

hi, i am new here.
i have issues with Python IDLE 3.13.15 under Windows 11.

  1. if i have entries under “File|Recent Files >” in Python IDLE Shell where the underlying file does not exist anymore, and i click that entry, a new Python IDLE editor window opens with nothing in - but i am not able to close that window anymore with the X on top right corner, nor option “File|Close Window Alt-F4” nor “Exit IDLE Ctrl-X”. only the task manager was able to kill the process.
  2. if i try to run a python script from Python IDLE editor with “Run|Run… Customized Shift-F5” and you want to type in a filename with filepath e.g. “C:\\path with spaces\\file name with spaces.extension” and after execution the script if you opens that Run… Customization dialog again, the previous types string is screwed up. \\ and " missing, so you can’t just execute the script with the same parameters you typed in before, because they are not the same as before anymore. you have to type in everything again.
  3. if i want to open a python script file i go to “File|Open… Ctrl-O” and an open file dialog opens. but in that dialog “Text files (*.txt)” is the preselected file type - so you don’t see your python script files. you first have to change the preselection to “Python files” so get the python scripts listet. you have to do that every time you want to open a python file.

Python was installed under:
C:\Users\username\AppData\Local\Programs\Python\Python313
i don’t remember how it was installed - via Microsoft Store, via winget or via installation file from the python page.

if this is not the right place to report these issues, pleade tell me where the right place ist for that.

2

This sounds like three separate IDLE behaviors. For the stale Recent Files item, close IDLE and rename %USERPROFILE%\.idlerc\recent-files.

For the Run Customization problem, capture the exact value before and after reopening, especially whether the field is an argument list or a script path. A Windows path with spaces needs quoting, but IDLE’s dialog should preserve it; if it drops backslashes or quotes consistently, that sounds like a reproducible IDLE bug rather than Python parsing. A temporary workaround is to launch the script from a terminal with quoted arguments and print sys.argv to verify what arrives.

The Open dialog filter is a separate UI setting; note whether it resets every session. Include the exact Python and Windows versions, how Python was installed, and a minimal reproduction when reporting it. You can also run `python -m idlelib` from the same installation to confirm that the IDLE you launch belongs to the expected Python 3.13.15 copy.lst if it exists, rather than deleting it, then restart; that resets the list and is reversible. If the empty editor window is still unclosable after that, reproduce it with a clean IDLE configuration so it can be separated from the recent-file entry.

3

Hi Helen, thank you for your answer.
for the issue with “Run… Customized” i tried
the simple test script:

import sys; print(sys.argv[1:])

at first “Run…Customized”, i typed in:

xyz "C:\abcd feg\123.txt"

at second “Run…Customized”, the previous entered text altered to:

xyz {C:\abcd feg\123.txt}

at third “Run…Customized”, the previous altered text altered to:

xyz \{C:abcd feg123.txt\}

at that point the text does not alter anymore.

the script output of the runs above
at first run:

['xyz', 'C:\\abcd feg\\123.txt']

at second run:

['xyz', '{C:abcd', 'feg123.txt}']

at third run:

['xyz', '{C:abcd', 'feg123.txt}']
4

It looks like this is a reported bug and the fix is awaiting review:

5

yes, all my issues were fixed.
first issue with the recent files is already fixed in release 3.14.7.
Run... Customized fix is awaiting release.
open file dialog fix is also already awaiting release.