This section of our beginning python training class always stumps students.  Firstly, because they need to know the difference between a function and a method.  Secondly, they need to understand object oriented programming concepts.  Thirdly, they need to realize that python has three types of methods.  Then they need to know how to use each method, which means they need to know the purpose of each method type.  Then they have to understand mutable versus non-mutable types.  The list goes on.  As part of our python tutorial, I hope to shed some light on this confusing topic.

To begin, the difference between a function and a method in python is that a method is defined within a class.  Here is an illustration:

#function

	def greeting():
	                print "Hello, I hope you're having a great day!"

	class HSGPrinter(object):
	                #method
	                def greeting(self): 
	                                print "Hello, I hope you're having a great day!"

As should be obvious, the second definition of greeting is encapsulated within the HSGPrinter class and is , therefore, refered to as a method.

The astute reader will notice that the greeting method contains one parameter named self.  For those who know C++ , Java or C#, self is equivalent to this i.e. it is a reference to the invoking object:

I’ll get straight to the point.  Why should companies invest more in management training?  Here are 10 simple reasons.

1) An employee’s relationship with his or her direct manager is the most important single factor in employee engagement.

2) Engaged employees are happier and more productive.  Disengaged employees are frustrated and more disruptive.

3) Because there’s no widely agreed-on skillset for management (good managers come in all shapes and sizes), there’s an assumption everyone knows how to do it.  This is akin to someone who’s never driven before being given keys to a car and told: “Drive.”  (Many many years ago, this is how I first learned to manage.  I blundered my way through it.  Trial and error.  It wasn’t pretty.)

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

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!

The python keyword global is used in a function to distinguish a local representation of a variable with the same name. 

glbvar = 0

def setglbvar():
    global glbvar # include this declaration so that updates to glbvar are NOT LOCAL to this function
    glbvar = 1

def printglbvar():
    print glbvar     # No need for global declaration to read value of globvar

setglbvar()
printglbvar()       # Prints 1