Skip to content

Fix incorrect backticks #1560

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
merged 1 commit into from
Aug 12, 2020
Merged

Fix incorrect backticks #1560

merged 1 commit into from
Aug 12, 2020

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Aug 12, 2020

Like #1559, for:

  • PEP 445
  • PEP 467
  • PEP 548
  • PEP 621

Found with:

$ git grep "[A-Za-z0-9]\`\`[A-Za-z0-9]"
pep-0445.txt:``PyMem_Realloc()`` indirectly call``PyObject_Malloc()`` and
pep-0467.txt:This PEP proposes that ``bytes`` and ``bytearray``gain an optimised
pep-0548.rst:Reading this we first see the``break``, which obviously applies to
pep-0621.rst:for using``long_description`` and a corresponding

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent!

I wonder if we could have a PEP linter that rejected such mistakes in new contributions.

@gvanrossum gvanrossum merged commit 3301169 into python:master Aug 12, 2020
@hugovk hugovk deleted the fix-backticks branch August 12, 2020 16:15
@hugovk
Copy link
Member Author

hugovk commented Aug 12, 2020

Yes, I was about to add one to avoid the single backticks, and it's based on grep, so I'll see about adding a rule for this too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants