This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ThomasAH
Recipients Alan.Williams, Arfrever, ThomasAH, benjamin.peterson, christian.heimes, eric.araujo, eric.snow, georg.brandl, hasufell, hynek, iankko, jaraco, jdemeyer, jwilk, ncoghlan, robertwb, schmir, tarek, vbraun, vstinner
Date 2018-02-07.10:34:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I just stumbled across this problem when starting "idle3" in a directory containing a copy of which was not compatible with python3.

In issue13506 idle3 was changed to behave like the regular python shell, i.e. as described here in this issue, and since my ~/ imports readline, I could reproduce this problem by creating a bogus file and starting a python interpreter.

So besides being a security issue when starting python or idle in untrusted directories, it may cause technical issues when working in directories containing .py files with certain names.
Date User Action Args
2018-02-07 10:34:54ThomasAHsetrecipients: + ThomasAH, georg.brandl, jaraco, ncoghlan, vstinner, christian.heimes, schmir, robertwb, benjamin.peterson, tarek, jwilk, eric.araujo, Arfrever, iankko, eric.snow, hynek, jdemeyer, Alan.Williams, vbraun, hasufell
2018-02-07 10:34:53ThomasAHsetmessageid: <>
2018-02-07 10:34:53ThomasAHlinkissue16202 messages
2018-02-07 10:34:53ThomasAHcreate