[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [pygame] Speed *triples* by changing 'apply(f, args)' to 'f(*args)'
- To: <pygame-users@seul.org>
- Subject: RE: [pygame] Speed *triples* by changing 'apply(f, args)' to 'f(*args)'
- From: "Simon Wittber (Maptek)" <Simon.Wittber@perth.maptek.com.au>
- Date: Wed, 5 Mar 2003 15:31:58 +0800
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Wed, 05 Mar 2003 02:32:11 -0500
- Reply-to: pygame-users@seul.org
- Sender: owner-pygame-users@seul.org
- Thread-index: AcLi5qYpCnkS1O7iQd6Srojlgqng+gAAn2nA
- Thread-topic: [pygame] Speed *triples* by changing 'apply(f, args)' to 'f(*args)'
IIRC the apply builtin is now deprecated.
It might be issuing deprecation warnings every time it is called!
Simon.
-----Original Message-----
From: Pete Shinners [mailto:pete@shinners.org]
Sent: Wednesday, 5 March 2003 7:20 AM
To: pygame-users@seul.org
Subject: Re: [pygame] Speed *triples* by changing 'apply(f, args)' to
'f(*args)'
Gerrit Holl wrote:
> Then I changed in sprite.py:311, apply(f, args) to f(*args).
> Framespeed tripled:
i'm curious about the 'warning' you are getting. can you run with the
"-W all" flags under python, that should print all the warnings you are
getting. my version currently runs the same speed either way, but i am
not seeing any kind of warnings getting triggered. i'm also checking
against 2.3a2
--
"if they keep silent, the very stones will cry out" pete*shinners.org
____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org
____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org