Windows 'Edit with IDLE' fails in one directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
f:\dev\3x>py -m idlelib f:/dev/tem/blank.py opens blank.py in IDLE. But in File Explorer, right click on blank.py and selection of `Edit with IDLE => Edit with IDLE 3.13 (64 bit) fails. Nothing happens. Same for 3.12 and 3.11.
Copy blank.py up to f:/tem and Edit with IDLE works. Neither directory has __init__ and __main__ defined. Looking at all tabs of the respective properties dialogs and the only difference I noted was the content file and bytes numbers. Context-menu opening works in another existing dir, with the two dunders defined.
If .../tem is renamed or copied (and - removed from the copy name), the command-line success and context-menu failure remain. It seems to be poisoned somehow. With a new subdirectory, F:/dev/temNew with blank.py copied into it, context-menu selection works.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure through File Explorer's “Edit with IDLE” context-menu command for f:/dev/tem/blank.py, then compare it with the working command-line launch and the working temNew directory. Trace the Windows context-menu launch path and identify why this directory-specific case produces no visible result; done means the context-menu action opens the file reliably in IDLE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100