Python uses duck typing.
If it looks like a duck, and if it quacks like a duck then it is probably something that wants you to think it is a duck.
I would prefer perl above python if the language alone was taken into consideration.
Unfortunately I have a limited amount of space in my head and time is also a one-way street.
As I wrote before, I started using python because it's used as a scripting language in almost all the open source tools I use. And I'm really hoping for Python4 with strong typing and without the ridiculous whitespace dependency, but it's one of the compromises in life.
That is mostly a perfect definition.
I need to reinforce it with some worth points as well:
- While python insists of being strangely "object" only dependent..
- It will not suit a *NIX environment properly
- Example *before* the flames arise:
** Look how python interact with "PIPES" (primary building block of good OS)
** they crafted a totally wacko object "module" with a more odd thing...
** which oddly enough they call "template" (which you derive a pipe from)
- Now compare that with how PERL interacts *DIRECTLY* with PIPES
using a dozen direct ways to handle PIPES.
- Just a simple start point of comparison.. extend that to signals
- sockets... and process handling. Python is brain damaged doing that
Now look how a simple version "upgrade" will write a totally new
library set of *ALL* that crappy objects...
Honestly.. python is far from consideration being a proper SHELL
script admin tool.. more likely a VB kinda wanna be
Flames are welcome - I know some die hard folks are python enthusiasts..
I just do not figure out why
Paul