[issue22704] Review extension enable options

[Terry J. Reedy]

Terry J. Reedy  added the comment:

#27099 converted extensions to features always enabled for when they apply to.

--
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22704] Review extension enable options

[Terry J. Reedy]

New submission from Terry J. Reedy:

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.

--
assignee: terry.reedy
components: IDLE
messages: 229846
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Review extension enable options
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22704
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com