Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix typos in documentation #13344

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.

Sign up for GitHub

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 3 commits into from
May 16, 2019
Merged

Fix typos in documentation #13344

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5af2375
Fix typo in docs
tirkarthi May 15, 2019
0dbdf38
Do idle.rst change separately
terryjreedy May 16, 2019
891ecff
ditto
terryjreedy May 16, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Doc/faq/programming.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -792,7 +792,7 @@ Its documentation looks like this::
invoked using the three argument form.

The slash at the end of the parameter list means that all three parameters are
positional-only. Thus, calling :func:`pow` with keyword aguments would lead to
positional-only. Thus, calling :func:`pow` with keyword arguments would lead to
an error::

>>> pow(x=3, y=4)
Expand Down
2 changes: 1 addition & 1 deletion Doc/library/pickle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -642,7 +642,7 @@ or both.
by other classes as long as they implement :meth:`__setitem__`.

* Optionally, a callable with a ``(obj, state)`` signature. This
callable allows the user to programatically control the state-updating
callable allows the user to programmatically control the state-updating
behavior of a specific object, instead of using ``obj``'s static
:meth:`__setstate__` method. If not ``None``, this callable will have
priority over ``obj``'s :meth:`__setstate__`.
Expand Down