On Wed, Dec 1, 2010 at 10:26 AM, Jonathan Hartley <[email protected]> wrote:
> From your tone I infer I should beware of intermittent and
> unrepeatable problems.
Tone was intended to be helpful ;-) Any bugs introduced in a
transition would typically be quite repeatable and obvious. Now,
switching from pyglet to C-based calls via cython, there's a source of
real crashing bugs and other oddities :-) [oh, how I haven't missed
you, Bus Error]
> Cythoning is going well, in half-hour snatches over breakfast and
> lunch! Doubled my frame rate with the low-hanging fruit (type tags in
> my inner render loop.) Now I'm doing judicious bits of my matrix
> class, which should leave me with 100% 'white' source lines in my
> inner render loop ('white' as in the colored output of "cython -a".)
> Published results soon.
Awesome. Indeed I've also found that the cython'ing mostly helps when
applied to intensive Python calculation code, rather than just
cython'ing some random calls into OpenGL. My core "render a bunch of
landscape segments" code is cython'ed because it operates on actual C
structures so I've not actually compared how it performs to a vanilla
Python loop.
A little judicious use can go a long way :-)
Richard
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en.
