Welcome to Coders’ Liberation

I’ve been coding in Python for the last year, and although I still consider myself to be a ‘n00b’ I thought that it would be useful to share some of my adventures with this AWESOME language over the coming months.

I intend to share a little of my thoughts, HOW-TO’s, and many great resources for all those people out there who are aspiring Pythonistas!!

Hopefully there will be a little for everyone to feel liberated in their Python adventures.

Thank you for taking the time to visit!!!

IDE or not to IDE

Hey guys & dolls,

When I first started coding in Python I used an interactive shell, namely IDLE, to…lets say ‘wet my lips’ a little before deciding whether or not Python was the language for me. As a result I strongly recommend that unless your dealing with functions and classes (OOP) to just stick with the interactive shell (yes, it’s a pain, but it’s a worthwhile learning curve).

HOWEVER if your really loving Python, and I hope that you are, then for ease of use and flexibility I would highly recommend installing an IDE (Workbench) to use…..

“IDE – Integrated Development Environment”

Go to Wiki Python – http://goo.gl/uSmeqa – for a comprehensive list!

I use PyDev – http://pydev.org/ – it’s pretty awesome and highly dynamic.

That’s it for now!!

Python Communities

The more (good) friends you have in the Python world the quicker problem your problems will be resolved…..my advice: join active communities!

I have found the following to be an invaluable source of knowledge:


  • Google+ Python Community – if you’ve got a gmail account then sign in, else sign up!!
  • Stack Overflow – http://stackoverflow.com/

Why procrastinate!?!?!

The Zen of Python, by Tim Peters

>>> import this


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!