Python hits the spot
Armin Steinhoff
a-steinhoff at web.de
Sun Jun 23 07:56:30 EDT 2002
Siegfried Gonzi <siegfried.gonzi at kfunigraz.ac.at> wrote in message news:<3D1482AE.8FA299D8 at kfunigraz.ac.at>...
> A few weeks ago I complaint here that Python on Windows XP sucks. I had
> a problem which would took theoretically about 1.5 hours; but in reality
> it takes 6 hours on Windows XP and Python 2.2. After that 6 hours I must
> reboot my system in order to work on.
>
> In the following I got the advice to install a real user system on my
> laptop. Okay, I bought Linux SuSE 8.0 and installed it on my laptop (256
> MB RAM, 1000 MHz Celeron). I also installed Python 2.2 (the ActivePython
> version, otherwise I couldn't install idle due to the annoying
> "free_software_garbage_2_weeks_installation_nightmare").
It seems you have not a way with that "free_software_garbage"
> SWIG helped me to make my external Python C function (with gcc); and
> F2PY helped me to create my external Python Fortran 90 function (with
> the Intel Fortran 95 compiler).
>
> The directories and all the other programs and data are the same as on
> Windows.
>
>
> 1. After starting the process from within idle the complete system
> freezes after the first wavelength (after about 20 minutes). I couldn't
> kill a process or open a different session (via F2) in order to kill
> python. The last resort: turn off the power supply.
Seems so that _YOUR_ Python version shuts down the whole machine ...
It's simple -> BS in means BS out :)
> 2. I thought it is better to start the process from the command line and
> in a X terminal: python forcing.py
> The same behavior as aforementioned: last resort: power supply.
Your (extended) Python version seems to be really CRAPPY !!
> That is
> really good and fine because a Linux system really is greedy for "shut
> down immediately".
>
> 3. I thought it has to do with Gnome and I logged in to a KDE session.
> Same behavior as in point 1. and 2.
Why the heck should your problem related to Gnome or KDE ??
_YOU_ have implemented a problem into Python ...
(geborener Weltmeister ??)
> My conclusion: I will rewrite my simulation in Fortran 90 and will
> abadon Python.
Your problem has nothing to do with Python ... your implementation is the problem.
>Python is maybe good for some small scripts but not
> appropiate for serious programming.
Just bizarr!! Are you able to do serious program development??
Have a look to the SQL database 'gadfly' ... and then tell me again
that Python isn't appropriate for serious programming
> Thank you Billy Boy for a forgiving user system Windows XP
... and its crazy users :)
Armin
which in turn
> relieves Python's "wreak havoc" behavior.
>
> I cannot believe that Linux is responsible for Python's ill behavior
> under Linux. Before you start ranting about note the following: In a
> first step it has nothing to do with my programming style (admittedly
> not very good and famous) it has to do that the same calculation cannot
> be performed on Linux and Python 2.2!
>
>
> S. Gonzi
More information about the Python-list
mailing list