evilynux wrote:Just a quick note to warn alpha testers that current SVN version can fail to run.
This is partly because of issue 350 where i'm trying to find something that works for any python/pyopengl versions.
Basically, i'm optimizing opengl code for the transition to pyopengl3.x hence converting direct rendering mode (glBegin/glEnd) to array-based drawing. Array based drawing theoretically works with either 1) native python lists, 2) Numeric arrays or 3) numpy arrays.
1) is slower (at leasts that's what is said in the docs) but should work in every case
2) is suppose to work w/ both pyopengl2.x and pyopengl3.x. It's the case with my machines but isn't for at least one person.
3) requires a new dependency on numpy as it's not currently required.
I'd rather go with 3) but i don't know how much pain that would infer to Windows users.
The main reason being that when jumping to py2.5+pyopengl3.x we should move from Numeric to numpy.
Some have brought up possible audio issues with numpy [compared to Numeric] but iirc i managed to fix that (as well as getting completely rid of unmaintained PyOGG and PyVorbis) in the python2.5-experimental branch.
Any input from the active devs (e.g. MFH, Qstick, Akedrou, JohnStumpo, etc.) would be great. (Feel free to comment directly in issue 350).
Numeric = no longer supported, numpy = supported?
If that's the case... then it makes a lot of sense for us to migrate over to numpy
for future expandability and such. This will only break the alpha testers, as the
modules will all be included in any beta / RC / final versions. Besides, the alpha
testers should already be familiar with installing required modules to run from source.
I don't think it's a terrible thing to require alpha testers to download ctypes and
numpy in order to continue alpha testing, and we end up with a FoFiX that is more
compatible with future versions of Python and other dependencies.
---- EDIT ----
er, and Pyglet (you're still using Pyglet in place of PyOgg and PyVorbis, right?)