-
Notifications
You must be signed in to change notification settings - Fork 5.3k
tools: updating deprecation scripts #6289
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
Merged
alyssawilk
merged 4 commits into
envoyproxy:master
from
alyssawilk:flags_deprecation_script
Mar 25, 2019
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Looks good, but one slight Pythonic nit. Could we do
'\n'.join(email_snippets)'? That way the aboveappendbecomes a bit more declarative. Same forcode_snippets(and below..).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 can, but I'd prefer not to if I can talk you out of it :-)
If I pull newlines out of email snippets I think I should do it for the code for consistency. But for code it's a need-to-have and for email it's a nice-to-have to have the trailing \n after the join. I mean I could append another newline after both but if I want it after each snippet rather than between each snippet I think having it in the snippet rather than having it in the join is semantically correct.
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.
It's semantically correct, I'm just suggesting there are more Pythonic ways to do it if you're after Python style suggestions. Since the join value is substituted into a string in both cases, you can write something like
'foo bar:\n %s\n' % '\n'.join(stuff without any new lines in it). This discussion is really me being nit-picky, but reflects my understanding of Python best practices.