| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
An invalid color in a user highlight theme crashed the Settings dialog. Now it is ignored with a warning and the default color is used instead.
…be created IDLE now starts with default settings and shows a warning instead of exiting silently when started with pythonw. This also fixes the failure of the subprocess to connect in that case.
|
Does "Stacked on #157620." mean merge the other first? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
If the home directory does not exist and .idlerc cannot be created in the current directory, GetUserCfgDir() raised SystemExit at import of idlelib.config, before Tk was available, with the explanation only on stderr, which is invisible with pythonw. The same happened in the user-code subprocess, which imports idlelib.config too, producing the "IDLE's subprocess didn't make connection" error from the report.
Now GetUserCfgDir() returns '' and IDLE runs as it does in testing mode: default settings, nothing saved. The problems (a nonexistent home directory, a directory that could not be created) are reported in the configuration warning shown after the root is created, together with other configuration problems.
The other parts of the issue are already fixed: os.path.expanduser() on Windows ignores HOME since 3.8 and the user directory is computed once and used consistently, and printing to a None stderr no longer raises.
Stacked on #157620.
🤖 Generated with Claude Code