Skip to content

Conversation

@come-maiz
Copy link

@come-maiz come-maiz commented Jan 10, 2018

Fix typos found by codespell in docs, docstrings, and comments.

https://bugs.python.org/issue32746

Fix typos found by codespell.
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

Copy link
Member

@terryjreedy terryjreedy left a comment

Choose a reason for hiding this comment

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

All the changes are correct. Perhaps "that is" in 2 places would be even better than "that's". So 'Approved' once this change is considered.


# load_tests should have been called once with loader, tests and pattern
# (but there are no tests in our stub module itself, so thats [] at the
# (but there are no tests in our stub module itself, so that's [] at the
Copy link
Member

Choose a reason for hiding this comment

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

'that is' would maybe be even better

Copy link
Author

Choose a reason for hiding this comment

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

done.

version: 2.59

-- This set of tests primarily tests the existence of the operator.
-- Additon, subtraction, rounding, and more overflows are tested
Copy link
Contributor

Choose a reason for hiding this comment

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

This is an external source. I would prefer not to maintain our own version, even for typos.

Copy link
Author

Choose a reason for hiding this comment

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

reverted.

Copy link
Member

@ericvsmith ericvsmith left a comment

Choose a reason for hiding this comment

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

See _ctypes/libffi* comments. At this point we might not be forward or back porting any changes from upstream, but if someone wants to eventually do that or to use a new version, any extra diffs are going to make the task more difficult.

win32.S - Copyright (c) 1996, 1998, 2001, 2002 Red Hat, Inc.
Copyright (c) 2001 John Beniton
Copyright (c) 2002 Ranjit Mathew
Copy link
Member

Choose a reason for hiding this comment

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

I realize we have our own copy of libffi for Windows. Wouldn't changes to these files cause porting upstream changes more difficult? I suggest we not change any libffi files. See Modules/_ctypes/libffi_osx/README.ctypes.

Copy link
Author

Choose a reason for hiding this comment

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

reverted.

+---------------------------------------+ 160
| result area 8 |
+---------------------------------------+ 168
| alignement to the next multiple of 16 |
Copy link
Member

Choose a reason for hiding this comment

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

Same comment with this file:

I realize we have our own copy of libffi for OS-X. Wouldn't changes to these files cause porting upstream changes more difficult? I suggest we not change any libffi files. See Modules/_ctypes/libffi_osx/README.pyobjc.

Copy link
Author

Choose a reason for hiding this comment

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

reverted.

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

microphone input::

mixer.setrecsrc (1 << ossaudiodev.SOUND_MIXER_MIC)

Copy link
Contributor

@srinivasreddy srinivasreddy Jan 10, 2018

Choose a reason for hiding this comment

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

Pls do not remove existing lines. In other places too

Copy link
Author

Choose a reason for hiding this comment

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

I can revert this, but I'm curious, why do you want two empty lines at the bottom?

Copy link
Contributor

Choose a reason for hiding this comment

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

I am sorry. I didn't look at the file. If it is at bottom, you can keep it. I am worried about introducing unnecessary git diffs in the middle of a file.

Copy link
Contributor

@srinivasreddy srinivasreddy left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@ericvsmith ericvsmith dismissed their stale review January 17, 2018 13:48

OBE: libffi changes were removed.

@terryjreedy
Copy link
Member

terryjreedy commented Feb 2, 2018

Leo, it might have been better to open a bpo issue for changes to this many files, but I don't think it necessary now, so I am adding the skip labels now. I found your bpo user listing, with the same user name, but there is no indication you have signed the CLA. It would not be needed for any one of the typo fixes, so unless objects, I would let that pass.

The conflict in aclocal.m4 appeared to be because someone added, since this patch,

<blank line>
m4_include([m4/ax_check_openssl.m4])

at the bottom of the file, which conflicted with your removal of an extra blank line at the bottom without the context of the new line. In any case, I removed the context markers and left the addition alone. This should be rechecked after the retesting.

@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

@terryjreedy
Copy link
Member

A few changes have been reverted. Does anything think anything else should be?

@terryjreedy terryjreedy changed the title fix multiple typos bpo-32746: Fix multiple typos Feb 2, 2018
@terryjreedy
Copy link
Member

I decided a) to open an issue and b) to make this strictly about typos. After previous changes, there was only one whitespace deletion left (\n at the end of a data file).

Lib/opcode.py Outdated
def_op('BUILD_LIST', 103) # Number of list items
def_op('BUILD_SET', 104) # Number of set items
def_op('BUILD_MAP', 105) # Number of dict entries (upto 255)
def_op('BUILD_MAP', 105) # Number of dict entries (up to 255)
Copy link
Member

Choose a reason for hiding this comment

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

"(up to 255)" is outdated (in 3.6 too). Just remove it.

Copy link
Member

Choose a reason for hiding this comment

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

elopio or whoever makes the change should refresh the patch against master.

# (but there are no tests in our stub module itself, so thats [] at the
# time of call.
# (but there are no tests in our stub module itself, so that is [] at
# the time of call.
Copy link
Member

Choose a reason for hiding this comment

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

Close parenthesis.

aclocal.m4 Outdated
dnl
dnl Please remember that m4 expands AC_REQUIRE([PKG_PROG_PKG_CONFIG])
dnl only at the first occurence in configure.ac, so if the first place
dnl only at the first occurrence in configure.ac, so if the first place
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't configure be regenerated now?

Copy link
Member

Choose a reason for hiding this comment

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

I don't know and could not do so. Perhaps this should be reverted and either done separately, for 3.8 only, or left alone.

Copy link
Member

Choose a reason for hiding this comment

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

All 3 changes made. Anyone who wants to fix 'occurence' in aclocal.m4 for 3.8 and regenerate configure or whatever should do so separately.

@terryjreedy terryjreedy merged commit c3d9508 into python:master Feb 4, 2018
@miss-islington
Copy link
Contributor

Thanks @ElOpio for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Feb 4, 2018
Fix typos found by codespell in docs, docstrings, and comments.
(cherry picked from commit c3d9508)

Co-authored-by: Leo Arias <[email protected]>
@bedevere-bot
Copy link

GH-5520 is a backport of this pull request to the 3.7 branch.

@miss-islington
Copy link
Contributor

Sorry, @ElOpio and @terryjreedy, I could not cleanly backport this to 3.6 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker c3d9508ff22ece9a96892b628dd5813e2fb0cd80 3.6

terryjreedy added a commit to terryjreedy/cpython that referenced this pull request Feb 4, 2018
Fix typos found by codespell in docs, docstrings, and comments..
(cherry picked from commit c3d9508)
@bedevere-bot
Copy link

GH-5522 is a backport of this pull request to the 3.6 branch.

terryjreedy pushed a commit that referenced this pull request Feb 4, 2018
Fix typos found by codespell in docs, docstrings, and comments.
(cherry picked from commit c3d9508)

Co-authored-by: Leo Arias <[email protected]>
terryjreedy added a commit that referenced this pull request Feb 4, 2018
 Fix typos found by codespell in docs, docstrings, and comments.
Fixes for the following files were in post-3.6 code and not backported:
Lib/ctypes/_aix.py (new), Lib/test/test_concurrent_futures.py,
Modules/_asynciomodule.c, Modules/_pickle.c, Objects/obmalloc.c.

(cherry picked from commit c3d9508)
@come-maiz
Copy link
Author

thanks everybody!!! hugs

@come-maiz come-maiz deleted the typoss branch February 8, 2018 04:00
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.

10 participants