Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.6] bpo-27099: IDLE - Convert built-in extensions to regular featur… #3487

Merged
merged 1 commit into from
Sep 11, 2017

Conversation

terryjreedy
Copy link
Member

@terryjreedy terryjreedy commented Sep 10, 2017

…es (GH-2494)

About 10 IDLE features were implemented as supposedly optional
extensions. Their different behavior could be confusing or worse for
users and not good for maintenance. Hence the conversion.

The main difference for users is that user configurable key bindings
for builtin features are now handled uniformly. Now, editing a binding
in a keyset only affects its value in the keyset. All bindings are
defined together in the system-specific default keysets in config-
extensions.def. All custom keysets are saved as a whole in config-
extension.cfg. All take effect as soon as one clicks Apply or Ok.

The affected events are '<>', '<>',
'<>', '<>', '<>',
'<>', '<>', and '<>'. Any
(global) customizations made before 3.6.3 will not affect their keyset-
specific customization after 3.6.3. and vice versa.

Inital patch by Charles Wohlganger, revised by Terry Jan Reedy.
(cherry picked from commit 58fc71c)

https://bugs.python.org/issue27099

…es (pythonGH-2494)

About 10 IDLE features were implemented as supposedly optional
extensions.  Their different behavior could be confusing or worse for
users and not good for maintenance.  Hence the conversion.

The main difference for users is that user configurable key bindings
for builtin features are now handled uniformly.  Now, editing a binding
in a keyset only affects its value in the keyset.  All bindings are
defined together in the system-specific default keysets in config-
extensions.def.  All custom keysets are saved as a whole in config-
extension.cfg.  All take effect as soon as one clicks Apply or Ok.

The affected events are '<<force-open-completions>>', '<<expand-word>>',
'<<force-open-calltip>>', '<<flash-paren>>', '<<format-paragraph>>',
'<<run-module>>', '<<check-module>>', and '<<zoom-height>>'.  Any
(global) customizations made before 3.6.3 will not affect their keyset-
specific customization after 3.6.3. and vice versa.

Inital patch by Charles Wohlganger, revised by Terry Jan Reedy.
(cherry picked from commit 58fc71c)
@rhettinger
Copy link
Contributor

While this is difficult to review in detail, it looks good overall. +1 on moving forward with it.

@terryjreedy terryjreedy merged commit d6c397b into python:3.6 Sep 11, 2017
@terryjreedy terryjreedy deleted the backport-58fc71c-3.6 branch September 11, 2017 00:30
@terryjreedy
Copy link
Member Author

Thank you for taking a look. I used the news blurb to tell users what I think they need to know. I just posted to the issue a high-level 'developer' view of what the patch does. Even with that in mind, reviewing was tough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants