Skip to content
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

Merged
merged 2 commits into from
Nov 27, 2019
Merged

STY: F-strings #29870

merged 2 commits into from
Nov 27, 2019

Conversation

ShaharNaveh
Copy link
Member

Copy link
Member

@simonjayhawkins simonjayhawkins left a 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)}")
Copy link
Member

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?

Copy link
Member Author

@ShaharNaveh ShaharNaveh Nov 26, 2019

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).

Copy link
Member

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).

Copy link
Member Author

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.

Copy link
Contributor

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.

@simonjayhawkins simonjayhawkins added the Code Style Code style, linting, code_checks label Nov 26, 2019
@simonjayhawkins simonjayhawkins added this to the 1.0 milestone Nov 26, 2019
Copy link
Member

@WillAyd WillAyd left a 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

@jreback jreback merged commit 99cf733 into pandas-dev:master Nov 27, 2019
@jreback
Copy link
Contributor

jreback commented Nov 27, 2019

thanks @MomIsBestFriend

@ShaharNaveh ShaharNaveh deleted the STY-fstrings-pyx branch November 27, 2019 13:15
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code Style Code style, linting, code_checks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants