These are (mostly) all issues of personal opinion, but anyway...
On Tue, Aug 29, 2006 at 12:49:44AM -0400, Marcin Komorowski wrote:
>#!/usr/bin/env /usr/bin/pythonw
There's no point of using env if you specify an absolute path.
"#!/usr/bin/env pythonw" is probably what you want.
> def myDebug(
Marcin Komorowski wrote:
> Please kindly critique my code - what could I have done better? What
> would have made this code more Pythonic?
I now nothing of appscript, and didn't even read it all, but a comment
none the less.
> def myDebug( txt ):
> if txt == None:
> sys.stderr.flush
On Aug 29, 2006, at 2:46 AM, Dan White wrote:
you might already know the newest version of the intel compilers is
version 30...
so you might want to try that...
Thanks for the tip, Dan! But Intel screwed up my licensing on the
9.1.030 release, so I can't use it, I've been trying to get a li
On Aug 29, 2006, at 5:28 AM, [EMAIL PROTECTED] wrote:
> patches like this:
>
> # cd Python-2.5c1
> # patch -p0 < ~/Mac-PythonLauncher-Makefile.in.diff
> # patch < ~/configure.diff
>
>
> I invoked configure like this:
>
> # CC=icc CXX=icpc OPT="-xT -O3 -fstack-security-check -fpic -
> parallel" I
On 29-aug-2006, at 4:43, Boyd Waters wrote:
>
> On Aug 28, 2006, at 2:00 PM, Ronald Oussoren wrote:
>
>> IMHO only benchmarks will help us here. At the very minimal I'd like
>> to know how pystone compares on a python build with the Intel
>> compiler and the version of GCC that ships with Xcode.
On 29-aug-2006, at 4:28, Boyd Waters wrote:
>
> Feedback is welcome.
How fast is your intel-compiled version of python compared to a gcc-
compiled one? Pystone is a good first approximation for that.
Ronald
___
Pythonmac-SIG maillist - Pythonmac-S
