Re: [PyOpenGL-Users] Please test PyOpenGL 3.0.0c1
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@vr...> - 2009-02-16 20:33:55
|
Ben Smith wrote: > "Alternate" platform, Win XP SP3. bzr revision 67 > > I don't have any pyopengl apps of my own to try out, but I figure I > may as well report what I get from running the tests. I'm afraid I > haven't used pyopengl much, either, so pardon me if I make assumptions > about the code when I share a suggestion. Thanks a lot for testing, very helpful. > Python 2.5.1 > > C:\mypathisasecret\pyopengl\tests>python tests.py > ......No ARB imaging extension > ...E...OpenGL 1.2 support > ................. > ====================================================================== > ERROR: Test that we support framebuffer objects > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "tests.py", line 578, in test_fbo > glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, fbo) > File > "c:\python25\Lib\site-packages\OpenGL\platform\baseplatform.py", line > 275, in __call__ > return self( *args, **named ) > ArgumentError: argument 2: <type 'exceptions.TypeError'>: wrong type > > ---------------------------------------------------------------------- > Ran 30 tests in 22.968s > > FAILED (errors=1) This lends more strength to the idea that we've got a problem with 32-bit platforms with some integer-like types. Did you have numpy installed on 2.5.1? > Python 2.6.0 > > C:\mypathisasecret\pyopengl\tests>python26 tests.py > Traceback (most recent call last): > File "tests.py", line 6, in <module> > from Numeric import * > ImportError: No module named Numeric > > Obviously, in this case I don't have Numeric installed. A few minutes > of monkeying around didn't get me a numeric install from pypi or build > from source in python 2.6. This test maybe should be skipped for this > platform, for now, but I think it shouldn't stop the other tests from > running. I don't know how much more is expected to work without numpy > and on python 2.6. I've committed changes to the test suite so that it should skip all numpy-using tests if it can't import numpy. > Python 3.0.0 > > C:\mypathisasecret\pyopengl\tests>python30 tests.py > File "tests.py", line 5 > except ImportError, err: > ^ > SyntaxError: invalid syntax > > Probably smoother and more explicit to detect python 3000 and a > message about not supporting it. > > I don't mind submitting some hack and slash editing to get around > these, or trying out any changes. Python 3.x is going to require an extremely *large* amount of work to support. At this point I'm just not intending to work on 3.x support. Until there's some compelling reason for people to use 3.x I'm just too time-poor to be dedicating time to supporting it. I guess in theory we could hack around it by having a separate test suite that's imported solely if we're not on 3.x, but it seems like too much machinery for what's essentially going to be a "you're running 3.x, we don't support that" message. (3.x is going to fail, as you saw, even trying to compile the test module, so the driver script needs to be some hacked code that just checks for 3.x in a 3.x and 2.x compatible format and then does the import). Thanks a lot for your tests, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com |