Skip to content

Conversation

@csabella
Copy link
Contributor

No description provided.

@mention-bot
Copy link

@csabella, thanks for your PR! By analyzing the history of the files in this pull request, we identified @terryjreedy, @mlouielu and @kbkaiser to be potential reviewers.

@mlouielu
Copy link
Contributor

Do we need to document "method" in method? I thought that only needs to doc in class, not class' method.

@terryjreedy terryjreedy merged commit 36329a4 into python:master Jul 14, 2017
terryjreedy pushed a commit to terryjreedy/cpython that referenced this pull request Jul 14, 2017
…ConfigDialog (pythonGH-2697)

The will help writing dialog improvements and splitting the class into multiple classes.
Original patch by Cheryl Sabella.
(cherry picked from commit 36329a4)
terryjreedy added a commit that referenced this pull request Jul 14, 2017
…ConfigDialog (GH-2697) (#2702)

The will help writing dialog improvements and splitting the class into multiple classes.
Original patch by Cheryl Sabella.
(cherry picked from commit 36329a4)
@csabella csabella deleted the bpo30913 branch July 14, 2017 12:09
@csabella
Copy link
Contributor Author

@mlouielu
I don't think documenting methods within methods is typical, but, in this case, Terry wanted to do so in order to convert these methods into classes. Documenting it now both simplifies the refactoring and the docs can then be used within the class.

@terryjreedy
Copy link
Member

The grouping by tab page will immediately help with writing corresponding testcase classes.

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.

5 participants