pyopengl-users

[PyOpenGL-Users] Please test PyOpenGL 3.0.0c1

[Mike C. F. <mcf...@vr...>]

Hi all,

I'm intending to release approximately the current trunk of PyOpenGL in 
bzr as 3.0.0 final, barring any show-stopping bug reports.  So, if you 
have show-stoppers that haven't been addressed, let me know.  The 
3.0.0c1 release is basically the same as the b8 release with a few bug 
fixes and binary versions of GLUT and GLE32 for Win32 users.  Going 
forward, I'm thinking I may focus much of my energy on getting developer 
documentation and the like written so that more contributors can work on 
the package.  At some point I'd also like to revisit the idea of 
unifying the Pyglet and PyOpenGL generators so that we're able to avoid 
duplication of effort somewhat.

Downloads are available from:

https://sourceforge.net/project/showfiles.php?group_id=5988&package_id=6035

Enjoy yourselves,
Mike

-- 
________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com

Re: [PyOpenGL-Users] Please test PyOpenGL 3.0.0c1

[René D. <re...@gm...>]

Hi,

here's how you can test pyopengl.



1. run the unittests.  There's not many that come with pyopengl...
    python tests/tests.py
2. run your opengl programs unittests.
3. run your programs, and see if they work as expected.


When finished, please email back here your results.

Thanks!



#=========
#  here's how to download, build, install, and then test on unix
(ubuntu, debian, osx, etc) if you have bzr installed
(http://bazaar-vcs.org/).

bzr branch lp:pyopengl

cd pyopengl
python setup.py build
sudo python setup.py install
python tests/tests.py




#==========
#  here's results for unittests on one machine.

$ uname -a
Linux macpro2-linux 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC
2009 x86_64 GNU/Linux

$ python tests/tests.py
...........Warning: texture 2 residence expected 0 got 1
..OpenGL 1.2 support
.................
----------------------------------------------------------------------
Ran 30 tests in 8.440s

OK









On Sun, Feb 15, 2009 at 1:27 PM, Mike C. Fletcher
<mcf...@vr...> wrote:
> Hi all,
>
> I'm intending to release approximately the current trunk of PyOpenGL in
> bzr as 3.0.0 final, barring any show-stopping bug reports.  So, if you
> have show-stoppers that haven't been addressed, let me know.  The
> 3.0.0c1 release is basically the same as the b8 release with a few bug
> fixes and binary versions of GLUT and GLE32 for Win32 users.  Going
> forward, I'm thinking I may focus much of my energy on getting developer
> documentation and the like written so that more contributors can work on
> the package.  At some point I'd also like to revisit the idea of
> unifying the Pyglet and PyOpenGL generators so that we're able to avoid
> duplication of effort somewhat.
>
> Downloads are available from:
>
> https://sourceforge.net/project/showfiles.php?group_id=5988&package_id=6035
>
> Enjoy yourselves,
> Mike
>

Re: [PyOpenGL-Users] Please test PyOpenGL 3.0.0c1

[Ben S. <gu...@gm...>]

"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.



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)







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.



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.

-b


On Sun, Feb 15, 2009 at 4:00 PM, René Dudfield <re...@gm...> wrote:

> Hi,
>
> here's how you can test pyopengl.
>
>
>
> 1. run the unittests.  There's not many that come with pyopengl...
>    python tests/tests.py
> 2. run your opengl programs unittests.
> 3. run your programs, and see if they work as expected.
>
>
> When finished, please email back here your results.
>
> Thanks!
>
>
>
> #=========
> #  here's how to download, build, install, and then test on unix
> (ubuntu, debian, osx, etc) if you have bzr installed
> (http://bazaar-vcs.org/).
>
> bzr branch lp:pyopengl
>
> cd pyopengl
> python setup.py build
> sudo python setup.py install
> python tests/tests.py
>
>
>
>
> #==========
> #  here's results for unittests on one machine.
>
> $ uname -a
> Linux macpro2-linux 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC
> 2009 x86_64 GNU/Linux
>
> $ python tests/tests.py
> ...........Warning: texture 2 residence expected 0 got 1
> ..OpenGL 1.2 support
> .................
> ----------------------------------------------------------------------
> Ran 30 tests in 8.440s
>
> OK
>
>
>
>
>
>
>
>
>
> On Sun, Feb 15, 2009 at 1:27 PM, Mike C. Fletcher
> <mcf...@vr...> wrote:
> > Hi all,
> >
> > I'm intending to release approximately the current trunk of PyOpenGL in
> > bzr as 3.0.0 final, barring any show-stopping bug reports.  So, if you
> > have show-stoppers that haven't been addressed, let me know.  The
> > 3.0.0c1 release is basically the same as the b8 release with a few bug
> > fixes and binary versions of GLUT and GLE32 for Win32 users.  Going
> > forward, I'm thinking I may focus much of my energy on getting developer
> > documentation and the like written so that more contributors can work on
> > the package.  At some point I'd also like to revisit the idea of
> > unifying the Pyglet and PyOpenGL generators so that we're able to avoid
> > duplication of effort somewhat.
> >
> > Downloads are available from:
> >
> >
> https://sourceforge.net/project/showfiles.php?group_id=5988&package_id=6035
> >
> > Enjoy yourselves,
> > Mike
> >
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> PyOpenGL Homepage
> http://pyopengl.sourceforge.net
> _______________________________________________
> PyOpenGL-Users mailing list
> PyO...@li...
> https://lists.sourceforge.net/lists/listinfo/pyopengl-users
>

Re: [PyOpenGL-Users] Please test PyOpenGL 3.0.0c1

[Mike C. F. <mcf...@vr...>]

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