-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
STY: F-strings #29870
STY: F-strings #29870
Conversation
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.
@MomIsBestFriend Thanks for the PR. generally lgtm. minor comment.
@@ -234,7 +234,7 @@ cdef class Packer: | |||
default_used = 1 | |||
continue | |||
else: | |||
raise TypeError("can't serialize {thing!r}".format(thing=o)) | |||
raise TypeError(f"can't serialize {repr(o)}") |
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.
is there a reason not to use the !r
syntax?
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 just followed pep-498 (!s, !r, and !a are redundant
section).
Plus as someone who is new to python, at first I didn't understand the !r
syntax. I do think that if we use repr()
it will increase code readability (for new developers at least).
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.
fair enough but not seen this conversion in other PRs for #29547
to ensure consistency, could either update the issue with additional instructions or add a code check to disallow the redundant sytnax in f-strings (as a follow-on).
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.
Sure! love the idea of making a code style in the issue tab.
I don't have the confident to write this mini style guide, I really don't want to mislead people.
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.
@MomIsBestFriend ok if you'd make an issue about standarizing on repr(...) rather than !r
agree that its more explicit; we would need to change any code and add a code-check.
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.
lgtm. can you merge master? I think should help with CI
thanks @MomIsBestFriend |
black pandas
git diff upstream/master -u -- "*.py" | flake8 --diff