Python: Difference between revisions

From Fluids Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[File:Python.png|xkcd.com/353/|frame|<big></big>]]
* [[What is Python and Why Python?]]
* [[What is Python and Why Python?]]
* Randy LeVeque's [http://depts.washington.edu/clawpack/g2s3/slides/python-intro.pdf Intro to Python Tutorial Slides] (with introduction to NumPy)
* Randy LeVeque's [http://depts.washington.edu/clawpack/g2s3/slides/python-intro.pdf Intro to Python Tutorial Slides] (with introduction to NumPy)
* Find and replace strings in text files [[Replaceutil.py]]
* Find and replace strings in text files [[Replaceutil.py]]
* [[ Python Snippets | Odds and Ends / random useful snippets]]
=== Python 3 ===
[https://pythonclock.org The count-down is ticking.]
Python 2 is not going to be maintained past 2020.
If you're new to Python, start directly with Python 3, and you won't have to worry about it at all.
If you're a current Python 2 user, it's strongly recommended that you take the time to start converting to Python 3.


=== The Zen of Python ===
=== The Zen of Python ===
Line 31: Line 41:
  If the implementation is easy to explain, it may be a good idea.
  If the implementation is easy to explain, it may be a good idea.
  Namespaces are one honking great idea -- let's do more of those!
  Namespaces are one honking great idea -- let's do more of those!
----
<center>
[[File:Python.png|xkcd.com/353/]]
</center>

Latest revision as of 21:56, 13 December 2018

Python 3

The count-down is ticking. Python 2 is not going to be maintained past 2020. If you're new to Python, start directly with Python 3, and you won't have to worry about it at all. If you're a current Python 2 user, it's strongly recommended that you take the time to start converting to Python 3.

The Zen of Python

$ python
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!