Re: [PyOpenGL-Users] bug in glDrawBuffers?
Brought to you by:
mcfletch
From: Gijs <in...@bs...> - 2009-02-22 15:02:02
|
On 2/22/09 5:43 AM, Mike C. Fletcher wrote: > Mike C. Fletcher wrote: >> Gijs wrote: > ... >> ... >>> ctypes.ArgumentError: argument 2: <type 'exceptions.TypeError'>: >>> wrong type >>> >>> I tend to cast everything that needs to be passed to OpenGL and is >>> returned from OpenGL functions (like the genTextures and >>> genFramebuffers function). Guess I kinda got used to it but I knew >>> it wasn't normal. >> Okay, that would seem to be final confirmation that we have bugs in >> handling of numpy uints on 32-bit platforms. Luckily we now have a >> test-case I can run to provoke it :) . > Can you confirm that the machine exhibiting the problem is running > something less than Python 2.5.2? I can duplicate the effect on my > 32-bit Vista machine *only* if I downgrade to 2.5.1. Thinking back on > it, this must be the bug that we discovered which had us add the > ALLOW_NUMPY_SCALARS flag to the OpenGL.__init__ module. Thomas had > said he was intending to fix it in ctypes, and it looks like he did > just that in 2.5.2. 2.5.4 does not exhibit the problem. > > Assuming that you can confirm it seems we'll either have to tell > people to use >= 2.5.2 and/or document the use of ALLOW_NUMPY_SCALARS > for those weird cases where for some reason someone needs to use an > older version. Will need to test with Python 2.4 and/or stand-alone > ctypes to determine the versions to recommend. > > Thanks, > Mike > It's running Python 2.5.1. It is the standard version of Python that got delivered with Mac OS X 10.5. So unless people upgraded to a higher version of Python, it should affect everyone that's running Mac OS X 10.5. Regards, Gijs |