Re: [pygame] Pygame, clock.ticks() and 42

[andrew baker <failrate@xxxxxxxxx>]

Congratulations, you've found the answer to Life, the Universe, and Everything...

now you just need to find out The Question.

Seriously, though, is this a Douglas Adams joke embedded in the function call, or something?

On 9/3/05, Richard Jones < richardjones@xxxxxxxxxxxxxxxx> wrote:

I've just put up my team's final submission for PyWeek:

  http://www.mechanicalcat.net/tech/PyWeek/1/entrants/Uberteam

During final testing, we noticed something very odd: setting the Clock.ticks ()
value to 42 (or more) results in 100% CPU utilisation on my computer. 41
barely loads the system (ie. about 5-10% CPU). 42 is evil. This is just in
the title screen with no animation going on, nothing fancy. No music playing.
Weird, huh?

PyGame 1.7.1, PyOpenGL 2.0.1.08, Python2.4.1, Ubuntu Linux, SDL 1.2.7


    Richard

-- 
Andrew Ulysses Baker
"failrate"