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 ned.deily
Recipients dd789, ned.deily, ronaldoussoren, terry.reedy
Date 2020-03-13.02:16:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584065769.92.0.639071486001.issue39927@roundup.psfhosted.org>
In-reply-to
Content
As Ronald notes, the chdir to the user’s Documents folder is *only* needed when launching via IDLE.app (for example by double-clicking an IDLE.app icon in the macOS Finder) because the user has no control over the launched app’s working directory in that case and the default is inappropriate. Whereas, when launching IDLE from a command line (for example, with “python -m idlelib’), IDLE inherits the working directory of the UNIX shell process which the user has complete control over. This is how users experience IDLE today on all UNIXy platforms. Thus, the chdir location is correct and current code and behavior should not be changed except to catch a chdir failure. The only question is what to do when an exception is caught.
History
Date User Action Args
2020-03-13 02:16:09ned.deilysetrecipients: + ned.deily, terry.reedy, ronaldoussoren, dd789
2020-03-13 02:16:09ned.deilysetmessageid: <1584065769.92.0.639071486001.issue39927@roundup.psfhosted.org>
2020-03-13 02:16:09ned.deilylinkissue39927 messages
2020-03-13 02:16:09ned.deilycreate