python cheatsheets code example

Example 1: python cheat sheet

Best Python Cheat Sheet PDF:
https://websitesetup.org/wp-content/uploads/2020/04/Python-Cheat-Sheet.pdf

Example 2: python cheat sheet

print('Hello World') # print
string_name = "This is a string" # string
string_name[5:] # slicing returns "is a string"
integer_name = 4 # integer
float_name = 3.0 # float
list_name = ['a','b','cats','dogs', 1, 2.0] # list
list_name.append(3) # add to list
# list comprehension filters for int types from the previous list
list_comp = [x for x in list_name if type(x) is int]
# dictionary
dic = {"Bob":9766692343,"Alice":6123336678}
dic["Alice"] # returns 6123336678
dic_phone_numbers = dic.values() # returns list of values
dic_names = dic.keys() # returns list of keys
# class (cat object with 9 lives)
class Cat:
  def __init__(self,name):
    self.name = name
    self.lives = 9
    print(f"{name} is a cat!")
# recursive function (factorial example)
def factorial(x):
    if x == 1:
        return 1
    else:
        return (x * factorial(x-1))

Example 3: cheat sheet 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!

Example 4: python cheat sheet

Awesome Python Cheatsheet!