Date: Mon, 12 Dec 2005 12:46:40 -0800
From: larry price <[EMAIL PROTECTED]>
On 12/12/05, Bob Miller <[EMAIL PROTECTED]> wrote:
Patrick R. Wade wrote:
> I'm astonished. I was *sure* Larry would be the one to tell us to use
> Python.
No, it was my turn today. Larry will tell you to use Python tomorrow.
I forget whose turn it is on Wednesday.
wednesday is Rob Hudson,
Horst on thursday,
John Fleming on Friday,
OK -- it's Thursday, so it's my day.
You can speed up python code by compiling before execution.
Since python is referred to as an 'interpreted' language most people
forget it's actually the byte-code that runs on some PVM(i just made up
this term)
There are various ways of compiling. I usually take the lazy approach
through importing, e.g.
python -c 'import fix_aol_charset'
(note, I didn't type the .py)
The result is a .pyc file which you then call directly as:
python fix_aol_charset.pyc
In that case the leading '#!...' is not used/needed.
To see other options, like Optimize (=> .pyo) enter
python -h
Did I mention that you probably have to Ctrl-d out of the python -c '...'
command as Bob's example expects stdin (which you have to terminate)
- Horst (John, get ready --tomorrow is your day :-)
_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug
