I'm happy with Python 2.5
n00m
(Intel)] on win32
and Idon't move neither up nor down from it (the best & the fastest
version)
n00m
Just my an intuitive sensation, nothing objective in it.
Steven D'Aprano
Congratulations.
--
Steven
n00m
http://www.spoj.pl/submit/ There *was* Python 2.6.
Then admins shifted back to 2.5. People vote by their legs.
Grigory Javadyan
n00m
wrote:
> what the hell does that have to do with anything
>
> > Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit
> > (Intel)] on win32
>
> > and Idon't move neither up nor down from it (the best & the fastest
> > version)
> > --
> >http://mail.python.org/mailman/listinfo/python-list
>
>
Am I turmoiling your wishful thinking?
You may nourish it till the end of time.
n00m
Python's "print a * b" gets Time Limit Exceeded.
=============================================
PHP's code
=============================================
fscanf(STDIN, "%d\n", &$tcs);
while ($tcs--) {
fscanf(STDIN, "%s %s\n", &$n, &$m);
echo bcmul($n, $m, 0)."\n";
}
=============================================
does it in 4.8s
Tom Zych
> Am I turmoiling your wishful thinking?
> You may nourish it till the end of time.
Let us cease to nourish those fabled ones who dwell under bridges.
--
Tom Zych / freet...@pobox.com
Quidquid latine dictum sit, altum viditur.
Peter Parker
> n00m wrote:
>> Am I turmoiling your wishful thinking?
>> You may nourish it till the end of time.
>
> Let us cease to nourish those fabled ones who dwell under bridges.
>
LOL !
Ian Kelly
> http://www.spoj.pl/problems/TMUL/
>
> Python's "print a * b" gets Time Limit Exceeded.
If speed is the only thing you care about, then you can forget about
fretting over whether 2.5 or 3.1 is faster. You're using the wrong
language to begin with.
Steven D'Aprano
Surely that depends on whether you care about execution speed or
development speed.
--
Steven
Tom Zych
s/care/care more/. People generally care about both to /some/ extent.
(Probably being over-pedantic again...)
--
Tom Zych / freet...@pobox.com
"Would you like a lovely fluffy little white rabbit, little girl,
or a cutesy wootesly little brown rabbit?"
"Actually, I don't think my python would notice."
Michael Torrie
rr, is that you?
geremy condra
> n00m wrote:
>> Am I turmoiling your wishful thinking?
>> You may nourish it till the end of time.
>
+1 QOTW.
Geremy Condra
n00m
> On 02/27/2011 06:57 AM, n00m wrote:
>
> > Steve, see a list of accepted langs there, in bottom dropdown:
> > Then admins shifted back to 2.5. People vote by their legs.
>
> rr, is that you?
Are you asking me?
If so, my account there is http://www.spoj.pl/users/zzz/
n00m
The winner (just a schoolboy) of IOI 2009 lives in my town,
not very far from my house. I'm proud to have such a neibour.
His account on spoj: http://www.spoj.pl/users/tourist/
Of course he's also registered on many other online judge systems,
incl. www.topcoder.com
alex23
> http://www.spoj.pl/
There's your problem. I'd say most Python 3.x adopters are using it
for something other than working out whose performance dick is the
longest.
Steven D'Aprano
In fairness, the Python Dev team is very aware of the risk of performance
degradation. Performance is important, but it is not *so important* that
it outweighs everything else.
The question that needs to be asked is not "Is Python 3 fast?", but
instead "Is Python 3 fast enough?".
--
Steven
n00m
That's all what I meant to say in here.
User numerix (German?) knows ropes of Python miles
far better than e.g. me.
Brian
We want cake. And we need to eat it.
Doing a lot of instrument control and data acquisition stuff.
And a short dev period has same importance as short run time.
As for the safety of those that dwell under and walk over
bridges, yes I wrote a strain gage calibrator system that was
used by a civil engr for monitoring a bridge.
alex23
> The question that needs to be asked is not "Is Python 3 fast?", but
> instead "Is Python 3 fast enough?".
I'm certainly not going to argue against that, I just don't find the
coding contortions used on sites like spoj.pl for performance gains to
be anything approximating real world code. I will happily sacrifice
weird performance trickery for language consistency or performance
stability any day.
But at the same time, I read every single article on PyPy's ongoing
development that I can :)