bpo-36096: IDLE: Refactor class variables in colorizer#12002
Conversation
| @@ -0,0 +1 @@ | |||
| Refactor class variables to instance variables in colorizer. | |||
There was a problem hiding this comment.
For the present, I will take care of the idlelib news.txt entries.
There was a problem hiding this comment.
I should have asked this earlier, but once you approve a PR, should I then merge it? Thanks.
There was a problem hiding this comment.
If I check the []Approve box for a Review, and if you agree that it is ready, and accept the responsibility of doing the merge, yes. For most IDLE issues though, I consider the followup responsibility to be shared. If you prefer me to merge, say so. If a PR is actually a joint product, or if it is blocking doing another, I might merge it, but should say so first.
There was a problem hiding this comment.
Thank you, that's very helpful. I think this one looks OK and you've approved it, so I'll merge it soon.
|
Thanks @csabella for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
(cherry picked from commit ed1deb0) Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>
|
GH-12069 is a backport of this pull request to the 3.7 branch. |
|
|
|
Thanks @csabella for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
(cherry picked from commit ed1deb0) Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>
|
GH-12075 is a backport of this pull request to the 3.7 branch. |
|
As will nearly always be the case, these post-merge buildbot failure reports are 'false positives' in relation to the merge. Both are failures in test_urllib2net. Looking at https://buildbot.python.org/all/#/console, it appears that the two merges before this broke almost everything. |
|
You added the 'need backport to 3.7' label to the closed PR and it started the backporting process all over again? That's a good trick to know about! |
Refactor class variables to instance variables in
colorizer.py.https://bugs.python.org/issue36096