Posts Tagged With ‘Python&8217


Another Reason To Use Python

I don’t have enough time to blog these days but I tweet so frequently.  It sounds like a contradiction, huh? I spent my whole weekend trying to simulate standart and improved Booth Radix(2,4,8, and 16) Multipliers.

I decided to use python to implement the simulator. It’d be ruby, java … etc. but
timing was a big issue. I had to understand all the algorithms and implement, then, prepare a performance analysis report. Python saved my life, it took 2 nights to implement and port it as win32 application for windows users who don’t have python interpreter installed. It was quite useful to develop and share because If you are living in a third world country, you can share your (python, ruby, haskel,perl,ocaml …etc. ) project  source code with anyone
who asks it. Because, probably, most of the computer science (and engineering) students including graduate ones don’t know about the computer languages like python. Their response will be, “…mm, strange  … what does this small code snippet do? ….”. Yes, it is strange and that small piece of code is the core of the algorithm…. etc. People who have extreme D&D  (Drag & Drop) capabilities without knowledge are dominated in Turkey. Yes, I mean  Microsoftian people.

By the way, I’m trying to finialize my studies on IR (which is specific to Turkish language) to send it local conference which will be held in Harran Uni.

I didn’t mention about the new year as I did in the past because, things are same. I’m still:


Django 1.0

Django 1.0 released. I wanna try soon…


Monkey Patch

A monkey patch (also spelled monkey-patch, MonkeyPatch) is a way to extend or modify the runtime code of dynamic languages (e.g. Smalltalk, Javascript, Ruby, Perl, and Python) without altering the original source code.


Readers’ Choice Awards 2008

http://www.linuxjournal.com/article/10065


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!