bpo-30728: IDLE: Refactor configdialog to PEP8 names and add docstrings#2307
Conversation
There was a problem hiding this comment.
This should be in another issue (?), or do you want to PEP8 them, too? (I think this can be PEP8, too)
There was a problem hiding this comment.
My initial inclination was to leave this as is. But I found two issues patching config_key (as keybindingDialog): bpo-6739 and bpo-21519. (The patches overlap, but are not affected by the above.) With the file name changed in the diffs, I expect the patches would apply cleanly. I would like to verify the bugs, verify the fixes, add tests, and if appropriate, apply these patches, and possibly other more-or-less ready to go patches, before internal renaming.
There was a problem hiding this comment.
Remove. Fixed in a trivial PR.
There was a problem hiding this comment.
Explicit wrote down root and configure, too.
e.g. root = None, configure = None and add two blank line between them and class TestDialog
mlouielu
left a comment
There was a problem hiding this comment.
My computer dead at configdialog.py diff :(, I'll seperate by review.
There was a problem hiding this comment.
Remove blank line between FontTabTest and setUp or add the docstring
There was a problem hiding this comment.
There is also an extra blank above tearDownModule.
There was a problem hiding this comment.
dfont, dsize, dbold, may changed explicited to default_font, default_size, default_bold since it is testing about default settings.
There was a problem hiding this comment.
The function is actually about testing changes to 1 of the 3 items that define a font. I need to expand the name of the function and add a docstring that explains the issue and why the expected is what it is and what could go wrong. The short names are my laziness. If the longer names make the code easier for others to read, I will use them.
There was a problem hiding this comment.
Change the names. I will rewrite more later.
mlouielu
left a comment
There was a problem hiding this comment.
I leave some point, the comment first word should be capitalized.
There was a problem hiding this comment.
According to PEP328, this import should be used parentheses import like this:
from tkinter import (Toplevel, Frame, LabelFrame, Listbox, Label, Button, Entry,
Text, Scale, Radiobutton, Checkbutton, Canvas)
There was a problem hiding this comment.
I agree that this would be better.
There was a problem hiding this comment.
Revise import revision as suggested and leave in patch.
There was a problem hiding this comment.
Not add the variable name but add a blank line between self.geometry and comment.
There was a problem hiding this comment.
Just remove 'Theme Elements. ' and add a blank.
There was a problem hiding this comment.
For first patch, undo all changes to comments. We will revise them as per the suggestions in a follow-up patch.
Leave code changes in init.
There was a problem hiding this comment.
Comment first word should be capitalize Load
There was a problem hiding this comment.
In general, "comments should be complete sentences", with a space after '#', first word capitalized, and a period at the ending. # Load .... dict. Though contrary to much programmer practice, including my own once, I prefer to follow this.
Phrases are allowed (capitalized), and if short, the period can omitted. There are occasions where short phrases are appropriate, but they are far fewer than their use.
There was a problem hiding this comment.
As said above, table all suggested changes to comments for another patch. Changing comments can create merge conflicts that can not be mechanically fixed.
There was a problem hiding this comment.
This seems not used, but make it capitalized, and add a blank line.
There was a problem hiding this comment.
Some people believe that unused code == dead code and should be removed rather than be commented out indefinitely. At some point we should decide. Let's change this to
`# XXX Decide whether to keep or delete these key bindings.
Thinking about it, we bind Escape elsewhere and should here. F1 for help is standard. ^A for apply is not, but usability guidelines say dialogs should be usable without a mouse. On there other hand, Tab and Return should work. Future project: We should add 'IDLE Dialog Conventions' to README and follow consistently. Leave code commented out for now.
Keys for mouse actions is https://bugs.python.org/issue27620. I added a note there.
There was a problem hiding this comment.
Leave uncommenting for a later patch.
There was a problem hiding this comment.
Capitalized Create, Current
There was a problem hiding this comment.
Thank you Cheryl for the work this involved and Louie for the non-trivial review. I did not review every change but focused on Louie's comments, as they raise a couple of meta-issues of how much to do in one patch. As a result, I have a better idea how to move forward.
This PR does not belong to #27388. That aside, I think this PR does too much at once and may be pre-mature.
After submitting this, I will open a new issue for modernizing configdialog. Modernizing includes: adding docstrings; changing to PEP8 names; changing most comments to sentences; reviewing and possibly changing overly cryptic existing PEP8 names; and at least metaphorically, adding tests. For a large file like config dialog, I would like a separate PR for each of these.
Louie's comment on config_key got me thinking again about the problem of breaking existing tracker patches, especially any that are ready to go. There were no patches that I know of for textview and I don't intend to apply the existing one for About IDLE as is.
Many of the comments below also appear above as responses to Louie's comments. Most can also be understood as they are.There was a problem hiding this comment.
My initial inclination was to leave this as is. But I found two issues patching config_key (as keybindingDialog): bpo-6739 and bpo-21519. (The patches overlap, but are not affected by the above.) With the file name changed in the diffs, I expect the patches would apply cleanly. I would like to verify the bugs, verify the fixes, add tests, and if appropriate, apply these patches, and possibly other more-or-less ready to go patches, before internal renaming.
There was a problem hiding this comment.
I agree that this would be better.
There was a problem hiding this comment.
Just remove 'Theme Elements. ' and add a blank.
There was a problem hiding this comment.
# Dismiss dialog without saving.
# Apply changes and save.
`# Open context help.
There was a problem hiding this comment.
In general, "comments should be complete sentences", with a space after '#', first word capitalized, and a period at the ending. # Load .... dict. Though contrary to much programmer practice, including my own once, I prefer to follow this.
Phrases are allowed (capitalized), and if short, the period can omitted. There are occasions where short phrases are appropriate, but they are far fewer than their use.
There was a problem hiding this comment.
I might have once changed type to typ. Many consider reusing builtin names a bad idea in general. With syntax highlighting, it becomes visually distracting, misleadingly marking type as different from the other names. type_ could be used if type is really the proper name, but it is not here. config module uses type as a parameter name where it means bool or int, (but cls could be used instead). Here, typ is one of the keys in changed_items, defined just above, which correspond to the config files. These are not type-classes at all. typ should become file.
Changing existing pep8 names is not really part of this patch.
There was a problem hiding this comment.
Or # Get first part, up to first space.
Or delete, as it seems pretty obvious. x.split()[k] is a common idiom.
Or leave comments alone in this PR and revise them to PEP8 standards in a separate PR.
There was a problem hiding this comment.
There is also an extra blank above tearDownModule.
There was a problem hiding this comment.
The function is actually about testing changes to 1 of the 3 items that define a font. I need to expand the name of the function and add a docstring that explains the issue and why the expected is what it is and what could go wrong. The short names are my laziness. If the longer names make the code easier for others to read, I will use them.
terryjreedy
left a comment
There was a problem hiding this comment.
After reviewing existing patches and reviewing this one and thinking about my experience with merges, I decided what to revert or delay for a future patch, what to keep for this one (most of it), or add to this one Just a few things), with an eye to minimizing work over the next several patches for configdialog. More on the issue.
There was a problem hiding this comment.
Revise import revision as suggested and leave in patch.
There was a problem hiding this comment.
For first patch, undo all changes to comments. We will revise them as per the suggestions in a follow-up patch.
Leave code changes in init.
There was a problem hiding this comment.
As said above, table all suggested changes to comments for another patch. Changing comments can create merge conflicts that can not be mechanically fixed.
There was a problem hiding this comment.
Leave uncommenting for a later patch.
There was a problem hiding this comment.
Undo code change; we will review code later.
textAndTags => text_and_tags, by rule
txTa => texttag, as temporary custom replacement
There was a problem hiding this comment.
Code changes like should have been left for another patch, but they are here now and very unlikely to cause a problem since the extension tab is relatively new and should not be touched by existing patches.
There was a problem hiding this comment.
Change the names. I will rewrite more later.
|
I've made the changes to configdialog to only include the name changes and the code change in init. I hope I got the file to the correct state for review. |
terryjreedy
left a comment
There was a problem hiding this comment.
If no problems arise when I test the dialog, I will merge this.
|
I tested by trying out and applying an example of every possible change on configdialog and checking for the correct change in the user configuration files. (An editor that reloads changed files, Notepad++, was essential for this. ) |
from tkinter import *to import each name.