[Fwd: Re: [Uuu-devel] languages] <-- Why Python

[Ville Vainio]

>>>>> "Mike" == Mike Meyer <mwm at mired.org> writes:

    Mike> IPython's pysh seems a little clumsy for interactive use, as
    Mike> it requires special characters to distinguish between
    Mike> commands to be passed to the shell and commands to be passed
    Mike> to the scripting language. This should be contrasted with

What do you mean by "the commands to be passed to the shell"? Commands
on the path (the normal situation in Unix) can be executed directly
just like in bash et al. Ditto for "magic" functions if "automagic" is
on.

I only use ! for calling commands that are in the current directory. A
*real* deficiency with ipython/pysh under Linux is the lack of job
control (in the sense that ^z suspends the whole ipython). I don't see
why pysh would not be able to match and exceed the capabilities of
shell in job control as well. It's not a priority for fperez himself
ATM, but we'll see how easy it is to add shellish job control in the
future after the refactoring...

    Mike> I'll say it again - if you're arguing about which language
    Mike> to use, you're arguing about the wrong thing.

In a sense C is the native language of Unix and Windows (system calls
are in C). It might make sense to expose the OS as Python objects.

I work w/ Symbian OS in my day job, with the OS API in C++. I'm not
sure whether it's a good idea or not, but at least some people are
doing it :).

-- 
Ville Vainio   http://tinyurl.com/2prnb