Skip to content

Spelling fixes in style guide #183

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
kennethreitz merged 2 commits into from
Jul 28, 2012
Merged

Spelling fixes in style guide #183

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0a045fd
Fix spelling in style guide
thomasballinger Jul 5, 2012
a8e36af
fix grammar issues with style guide
thomasballinger Jul 5, 2012
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
10 changes: 5 additions & 5 deletions docs/writing/style.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ recognised fact that code is read much more often than it is written.
One reason for Python code to be easily read and understood is its relatively
complete set of Code Style guidelines and "Pythonic" idioms.

Moreover, when a veteran Python developer (a Pythonistas) point to some
Moreover, when a veteran Python developer (a Pythonista) point to some
parts of a code and say it is not "Pythonic", it usually means that these lines
of code do not follow the common guidelines and fail to express the intent in
what is considered the best (hear: most readable) way.
Expand Down Expand Up @@ -128,7 +128,7 @@ called with each recipient as an argument: ``send('Hello', 'God', 'Mom',
'Cthulhu')``, and in the function body ``args`` will be equal to ``('God',
'Mom', 'Cthulhu')``.

However, this construct has some drawback and should be used with caution. If a
However, this construct has some drawbacks and should be used with caution. If a
function receives a list of arguments of the same nature, it is often more
clear to define it as a function of one argument, that argument being a list or
any sequence. Here, if ``send`` has multiple recipients, it is better to define
Expand Down Expand Up @@ -156,7 +156,7 @@ Python functions that are:

* easy to read (the name and arguments need no explanations)

* easy to change (adding a new keyword argument do not break other parts of the
* easy to change (adding a new keyword argument does not break other parts of the
code)

Avoid the magical wand
Expand All @@ -178,8 +178,8 @@ possibilities, because it grows the confidence that no hard-wall will be on the
way. However, knowing how to use them and particularly when **not** to use
them is the most important.

Like a Kungfu master, a pythonistas knows how to kill with a single finger, and
never do it.
Like a Kungfu master, a Pythonista knows how to kill with a single finger, and
never to do it.

We are all consenting adults
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down