Last year, Hewlett-Packard purchased Autonomy for $10 billion, enduring a number of arrows from its competitor Oracle. What a difference a year is!

Since the purchase HP saw the leaving of Autonomy CEO Mike Lynch, which was not on friendly terms. It also saw the departure of the whole original management team and 20 percent of the staff. Now, the question is whether or not HP will see its move compensate or become another WebOS-style fiasco, marking the company needs to stay with hardware.

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:

Python programming language is general purpose open source programming language. One of its main features is flexibility and ease of use. Python has a variety of useful set of utilities and libraries for data processing and analytical tasks. Currently due to the rise in demand of big data processing python has grown in popularity because its features are easy to use which are core to the processing of huge chunks of information.

Guido Van Rossum, the pioneer of python, introduced python in the year 1980 and then implemented it in 1989. The intention behind the development of python was to make it open source language that can also be used for commercial projects. The fundamental principle of python is to write the code that is easy to use, highly readable and embrace writing fewer lines of code for achieving a particular task. One of the most popular standard libraries which have ready to use tools for performing a various work is Python Package Index. It was introduced in January 2016 and contains more than 72,000 packages for third-party software usage.

Python plays a critical role in linking data to customers. Recently python has found few entry barriers and many people have had access to have experienced the power of python in the past. So, what makes python the best language for big data analytics?

One of the reasons to choose python is that python ecosystem is very vibrant, the ratings at Redmonk are a proof of the strength python community. The Redmonk ranking is based on StackOverflow discussions and contribution made in Github to determine the popularity of programming language on the method used by users to ask questions about Python and the number of the open source projects contributions.

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!