mirror of
https://github.com/kennethreitz/python-guide.git
synced 2026-06-05 23:00:18 +00:00
Suggest improved introduction to Style/#Idioms
My reading, though limited, suggests that the general notion of Idioms is used often, but rarely explained. It feels very alien to beginners. A term like "Idiomatic Python" can cause mental stack overflow. It did to me :) So I humbly submit, in this case, explicit is better than implicit. I debated whether to place it at the top of the document, where idioms are first mentioned, but placed it here instead, as this section explicitly references the topic of idioms.
This commit is contained in:
+10
-1
@@ -251,7 +251,16 @@ is a probable indication that such a refactoring is needed.
|
||||
Idioms
|
||||
------
|
||||
|
||||
Idiomatic Python code is often referred to as being *Pythonic*.
|
||||
A programming Idiom, put simply, is _a way_ to write code. The notion of programming Idioms
|
||||
is discussed amply at `c2 <http://c2.com/cgi/wiki?ProgrammingIdiom>` and at `Stack Overflow <http://stackoverflow.com/questions/302459/what-is-a-programming-idiom>`.
|
||||
|
||||
Idiomatic Python code is often referred to as being *Pythonic*.
|
||||
|
||||
Although there usually is one-- and preferably only one --obvious way to do it;
|
||||
_the_ way to write idiomatic Python code can be non-obvious to Python beginners. So,
|
||||
good idioms must be consciously acquired.
|
||||
|
||||
Some common Python idioms follow:
|
||||
|
||||
.. _unpacking-ref:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user