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.

Title: Review extension enable options
Type: enhancement Stage: resolved
Components: IDLE Versions: Python 3.4, Python 3.5, Python 2.7
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: terry.reedy Nosy List: terry.reedy
Priority: normal Keywords:

Created on 2014-10-23 00:17 by terry.reedy, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg229846 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2014-10-23 00:17
Currently, each extension is supposed to have an 'enable' option and optionally enable_editor or enable_shell, to "to apply it only to editor/shell windows" (config-extensions.def comment).  I think the rule should be changed (see below).

Currently, the file itself does not follow its own rule.  Most editor-only options only have enable and not enable_editor.  One have enable and enable_shell=False, presumably to exclude the shell, but a user could override False with True, in the user config-extensions, which would not be valid.  The file should be changed to follow the current or altered rule.

I think that the requirement should be for the presence of any one of the enable options.  An extension that is only valid for the editor should simply have enable_editor.  Ditto for enable_shell. Enable by itself would globally turn the extension on or all for all windows, include output windows.  It is possible that we might need an enable_output option too.
msg336161 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2019-02-21 00:21
#27099 converted extensions to features always enabled for when they apply to.
Date User Action Args
2022-04-11 14:58:09adminsetgithub: 66893
2019-02-21 00:21:39terry.reedysetstatus: open -> closed
resolution: out of date
messages: + msg336161

stage: needs patch -> resolved
2014-10-23 00:17:04terry.reedycreate