Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

bpo-30728: IDLE: Refactor configdialog to PEP8 names and add docstrings#2307

Merged
terryjreedy merged 5 commits intopython:masterfrom
csabella:configdialog
Jun 26, 2017
Merged

bpo-30728: IDLE: Refactor configdialog to PEP8 names and add docstrings#2307
terryjreedy merged 5 commits intopython:masterfrom
csabella:configdialog

Conversation

@csabella
Copy link
Contributor

@csabellacsabella commentedJun 20, 2017
edited
Loading

  1. Changed CamelCase names to PEP8.
  2. Changefrom tkinter import * to import each name.
  3. Changed 'colour' to 'color' as mentioned in a bug report.
  4. Added docstrings.
  5. Typo in config_key fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This should be in another issue (?), or do you want to PEP8 them, too? (I think this can be PEP8, too)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

My initial inclination was to leave this as is. But I found two issues patching config_key (as keybindingDialog):bpo-6739 andbpo-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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Remove. Fixed in a trivial PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Explicit wrote downroot andconfigure, too.
e.g.root = None,configure = None and add two blank line between them and class TestDialog

Copy link
Contributor

@mlouielumlouielu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

My computer dead at configdialog.py diff :(, I'll seperate by review.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Remove blank line between FontTabTest and setUp or add the docstring

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

There is also an extra blank above tearDownModule.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Go ahead.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

dfont,dsize,dbold, may changed explicited todefault_font,default_size,default_bold since it is testing about default settings.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Change the names. I will rewrite more later.

Copy link
Contributor

@mlouielumlouielu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I leave some point, the comment first word should be capitalized.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

According toPEP328, this import should be used parentheses import like this:

from tkinter import (Toplevel, Frame, LabelFrame, Listbox, Label, Button, Entry,    Text, Scale, Radiobutton, Checkbutton, Canvas)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I agree that this would be better.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Revise import revision as suggested and leave in patch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Not add the variable name but add a blank line betweenself.geometry and comment.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Just remove 'Theme Elements. ' and add a blank.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

For first patch, undo all changes to comments. We will revise them as per the suggestions in a follow-up patch.
Leave code changes ininit.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Comment first word should be capitalizeLoad

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

As said above, table all suggested changes to comments for another patch. Changing comments can create merge conflicts that cannot be mechanically fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This seems not used, but make it capitalized, and add a blank line.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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 ishttps://bugs.python.org/issue27620. I added a note there.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Leave uncommenting for a later patch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedAvoid

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedUser

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedUser

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedCreate,Current

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedSet

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

CapitalizedCreates

Copy link
Member

@terryjreedyterryjreedy left a comment
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

My initial inclination was to leave this as is. But I found two issues patching config_key (as keybindingDialog):bpo-6739 andbpo-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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I agree that this would be better.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Just remove 'Theme Elements. ' and add a blank.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

# Dismiss dialog without saving.
# Apply changes and save.
`# Open context help.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I might have once changedtype totyp. Many consider reusing builtin names a bad idea in general. With syntax highlighting, it becomes visually distracting, misleadingly markingtype as different from the other names.type_ could be used iftype is really the proper name, but it is not here. config module usestype as a parameter name where it meansbool orint, (butcls 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 becomefile.

Changing existing pep8 names is not really part of this patch.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Good idea.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

There is also an extra blank above tearDownModule.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

@terryjreedyterryjreedy changed the titlebpo-27388: IDLE: Refactor configdialog to PEP8 names and add docstringsbpo-30728: IDLE: Refactor configdialog to PEP8 names and add docstringsJun 21, 2017
Copy link
Member

@terryjreedyterryjreedy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Revise import revision as suggested and leave in patch.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

For first patch, undo all changes to comments. We will revise them as per the suggestions in a follow-up patch.
Leave code changes ininit.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

As said above, table all suggested changes to comments for another patch. Changing comments can create merge conflicts that cannot be mechanically fixed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Leave uncommenting for a later patch.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Undo code change; we will review code later.
textAndTags => text_and_tags, by rule
txTa => texttag, as temporary custom replacement

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Uncomment for now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Go ahead.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Change the names. I will rewrite more later.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

But leave alone for now.

@csabella
Copy link
ContributorAuthor

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.

Copy link
Member

@terryjreedyterryjreedy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

If no problems arise when I test the dialog, I will merge this.

@terryjreedy
Copy link
Member

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. )

@terryjreedyterryjreedy merged commitbac7d33 intopython:masterJun 26, 2017
terryjreedy pushed a commit to terryjreedy/cpython that referenced this pull requestJun 26, 2017
…2307)Also, change '*' in the tkinter import to an explicit list of names.Patch by Cheryl Sabella.(cherry picked from commitbac7d33)
@csabellacsabella deleted the configdialog branchJune 26, 2017 22:46
terryjreedy added a commit that referenced this pull requestJun 27, 2017
…2421)Also, change '*' in the tkinter import to an explicit list of names.Patch by Cheryl Sabella.(cherry picked from commitbac7d33)
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@terryjreedyterryjreedyterryjreedy approved these changes

+1 more reviewer

@mlouielumlouielumlouielu requested changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@csabella@terryjreedy@mlouielu@the-knights-who-say-ni

Comments


[8]ページ先頭

©2009-2026 Movatter.jp