1. If you open a Python interpreter, and type

, it outputs the following:

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!

2. On python interpreter typing from __future__ import braces

it prints the output as follows Traceback (SyntaxError: not a chance (<interactive input>, line 1)

3. On python interpreter type import __hello__

this outputs Hello world…

Those were few easter eggs which were there in Python pre-3000 release

An antigravity module is added to Python 3.0. Importing the module opens a web browser to an xkcd comic that portrays Python having an antigravity module

Kindly let me know if you know any more easter eggs.

Ballmer Peak

I agree with Ballmer’s Peak; personal experience if you have proper quantity of alcohol and than do coding you are highly efficient but have no comments on whats that quantity as when I try I am not able to reach to that level but some time it happens on its own.

So alcohol is good for programmers; just kidding.

Comic on Microsoft and OpenSource