-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Refactor: Consolidate 'import textwrap' in core #34113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Lee-W
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit curious about why we want to do it this way. Also, would it make sense if we document these changes somewhere in the contribution document so that newcomers know what to follow?
Grepping and counting for imports of textwrap shows: the majority imports |
beae524 to
45fea83
Compare
Yep, sounds reasonable |
45fea83 to
a6c78b3
Compare
|
Can you please split this PR to 2 PRs (and possibly all other refactoring):
it would make things easier for release managers as providers releases are separated from airflow core |
a6c78b3 to
791c364
Compare
No description provided.