[Python-Dev] Re: Issue: 92359 - Python 3.10 IDLE 64-bit doesn't open any files names code (code.py, code.pyw) - found a partial fix but looking for input

On 5/14/2022 8:37 PM, Terry Reedy wrote: On 5/14/2022 12:40 AM, Guido van Rossum wrote: Probably "Edit with IDLE" should be changed. I have no idea where that is defined. I presume somewhere in PCBuild.  Steve Dower knows and is in charge of the Windows installer. FTR, the behaviour for

[Python-Dev] Re: Issue: 92359 - Python 3.10 IDLE 64-bit doesn't open any files names code (code.py, code.pyw) - found a partial fix but looking for input

On 5/14/2022 12:40 AM, Guido van Rossum wrote: So the "current working directory" is the directory containing the file, right? That would explain the behavior. Standard import shadowing. Probably "Edit with IDLE" should be changed. I have no idea where that is defined. I presume somewhere

[Python-Dev] Re: Issue: 92359 - Python 3.10 IDLE 64-bit doesn't open any files names code (code.py, code.pyw) - found a partial fix but looking for input

So the "current working directory" is the directory containing the file, right? That would explain the behavior. Probably "Edit with IDLE" should be changed. I have no idea where that is defined. In 3.11 we should be able to make that use the new -P option, which doesn't insert the working

[Python-Dev] Re: Issue: 92359 - Python 3.10 IDLE 64-bit doesn't open any files names code (code.py, code.pyw) - found a partial fix but looking for input

On 5/13/2022 9:20 PM, ward.dav...@gmail.com wrote: https://github.com/python/cpython/issues/92359 This is a specific (and now closed) example of import shadowing. The general issue is the subject of https://github.com/python/cpython/issues/67997 -- Terry Jan Reedy