GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||
GeezerVison is showing github.com — gh-119180: annotationlib: Fix __all__, other minor fixes by JelleZijlstra · Pull Request #122365 · python/cpython Conversation
|
| "call_evaluate_function", | ||
| "get_annotate_function", |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
These two were missing. The rest of the changes in this file are just formatting.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| self.assertIs(annotate_func, None) | ||
|
|
||
|
|
||
| class TestAnnotationLib(unittest.TestCase): |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This is the only non-formatting change in this file.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This is the first stdlib module we're proposing to use autoformatting for, is it worth checking on Discourse? Autoformatters are much more opionated than PEP 8, which may be a surprising experience for contributors (note @encukou ran into an issue with a similar tool just whilst making a change to a CPython-only docs extension).
A
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I hoped it wouldn't be controversial since we're already doing it for some of the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.