PyOpenGL

Evan Jones wrote:

> Actually, to be more specific, it's a problem with the OpenGL/GLU 
> module. I get the following error when I try and run any of the demos 
> that import it. The demos in OpenGL/Demos/GLE all work flawlessly.
>
>
> Traceback (most recent call last):
>   File "/sw/lib/python2.2/site-packages/OpenGL/Demo/NeHe/lesson1.py", 
> line 42, in ?
>     from OpenGL.GLU import *
>   File "/sw/lib/python2.2/site-packages/OpenGL/GLU/__init__.py", line 
> 32, in ?
>     GLUerror = __init___.GLUerror
> AttributeError: 'module' object has no attribute 'GLUerror'
>
>
> Now, I will admit that I'm trying to build on a bizarre configuration, 
> although when I built the "default" configuration it still failed with 
> the same error (although I'll double check this tomorrow). I'm using 
> Fink's Python (2.2.2) and I'm trying to build Togl. If I use "nm" on 
> the __init___.so, it doesn't show any "GLUerror" symbol, although the 
> .so in OpenGL/GL DOES have that symbol defined.
>
> Any ideas?
>
> Thank you for your assistance,
>
> Evan Jones
>
Which swig are you building with?

You should use 1.3.13

On Friday, May 9, 2003, at 00:49 Canada/Eastern, Rene Dudfield wrote:
>> Traceback (most recent call last):
>>   File "/sw/lib/python2.2/site-packages/OpenGL/Demo/NeHe/lesson1.py", 
>> line 42, in ?
>>     from OpenGL.GLU import *
>>   File "/sw/lib/python2.2/site-packages/OpenGL/GLU/__init__.py", line 
>> 32, in ?
>>     GLUerror = __init___.GLUerror
>> AttributeError: 'module' object has no attribute 'GLUerror'

> Which swig are you building with?
> You should use 1.3.13

I was actually not building with swig at all. I was assuming that the 
prebuilt wrappers would be sufficient. Is this not true? Are the 
prebuilt wrappers only for a specific platform or something?

Thanks,

Evan

--
Evan Jones: http://www.eng.uwaterloo.ca/~ejones/
"Computers are useless. They can only give answers" - Pablo Picasso

The distributed wrappers should, if I'm not mistaken, be sufficient for 
all platforms.  There should definitely be a GLUerror present in the GLU 
module, the module initialization code (in the included wrappers) 
explicitly imports it into the module dictionary.  Have you tried doing 
a completely clean install?  That is, removing any previous versions, 
deleting the "build" subdirectory of the source tree, then building and 
installing?

Good luck,
Mike

PS: are you working with Bernie on his Pythonic VR project, or is Python 
just taking over the entire Waterloo campus :) .  Almost makes me want 
to go back.

Evan Jones wrote:

> On Friday, May 9, 2003, at 00:49 Canada/Eastern, Rene Dudfield wrote:
>
>>> Traceback (most recent call last):
>>>   File 
>>> "/sw/lib/python2.2/site-packages/OpenGL/Demo/NeHe/lesson1.py", line 
>>> 42, in ?
>>>     from OpenGL.GLU import *
>>>   File "/sw/lib/python2.2/site-packages/OpenGL/GLU/__init__.py", 
>>> line 32, in ?
>>>     GLUerror = __init___.GLUerror
>>> AttributeError: 'module' object has no attribute 'GLUerror'
>>
...

> I was actually not building with swig at all. I was assuming that the 
> prebuilt wrappers would be sufficient. Is this not true? Are the 
> prebuilt wrappers only for a specific platform or something?

...

_______________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/

Just tried a clean install, and still got the same problem:

Traceback (most recent call last):
   File "/Users/rpm/Python/SimpleOGL.py", line 6, in ?
     from OpenGL.Tk import *
   File "/sw/lib/python2.2/site-packages/OpenGL/Tk/__init__.py", line 
14, in ?
     from OpenGL.GLU import *
   File "/sw/lib/python2.2/site-packages/OpenGL/GLU/__init__.py", line 
32, in ?
     GLUerror = __init___.GLUerror
AttributeError: 'module' object has no attribute 'GLUerror'

On Friday, May 9, 2003, at 09:05  AM, Mike C. Fletcher wrote:

> The distributed wrappers should, if I'm not mistaken, be sufficient 
> for all platforms.  There should definitely be a GLUerror present in 
> the GLU module, the module initialization code (in the included 
> wrappers) explicitly imports it into the module dictionary.  Have you 
> tried doing a completely clean install?  That is, removing any 
> previous versions, deleting the "build" subdirectory of the source 
> tree, then building and installing?
>
Rick Muller
rpm@...
http://wag.caltech.edu/home/rpm

On Friday, May 9, 2003, at 13:31 Canada/Eastern, Richard Muller wrote:
> Just tried a clean install, and still got the same problem:
>
> Traceback (most recent call last):
>   File "/Users/rpm/Python/SimpleOGL.py", line 6, in ?
>     from OpenGL.Tk import *
>   File "/sw/lib/python2.2/site-packages/OpenGL/Tk/__init__.py", line 
> 14, in ?
>     from OpenGL.GLU import *
>   File "/sw/lib/python2.2/site-packages/OpenGL/GLU/__init__.py", line 
> 32, in ?
>     GLUerror = __init___.GLUerror
> AttributeError: 'module' object has no attribute 'GLUerror'

Great! So I'm not on crack. The weird part is, I've talked to someone 
who said that they got it working. I'm getting them to email me a copy 
of their OpenGL directory and maybe that will help me figure it out.

--
Evan Jones: http://www.eng.uwaterloo.ca/~ejones/
"Computers are useless. They can only give answers" - Pablo Picasso

On Friday, May 9, 2003, at 12:05 Canada/Eastern, Mike C. Fletcher wrote:
> The distributed wrappers should, if I'm not mistaken, be sufficient 
> for all platforms.  There should definitely be a GLUerror present in 
> the GLU module, the module initialization code (in the included 
> wrappers) explicitly imports it into the module dictionary.  Have you 
> tried doing a completely clean install?  That is, removing any 
> previous versions, deleting the "build" subdirectory of the source 
> tree, then building and installing?

Yes, I have tried a completely clean install. I've even tried using 
"python setup.py build --force" with both swig 1.3.13 and swig 1.3.16. 
The former gives me the same error, and the latter doesn't even get as 
far (as expected). I'm wondering if it might be a problem with Mac OS 
X's "two level namespace" thing. I might have to investigate that.

> PS: are you working with Bernie on his Pythonic VR project, or is 
> Python just taking over the entire Waterloo campus :) .  Almost makes 
> me want to go back.

Actually, no, Python is just taking over. I'm taking CS488: Intro to 
Computer Graphics this semester, and it is being converted from Tcl/Tk 
+ OpenGL to Python/Tkinter + OpenGL, and I'm trying to get the 
environment working on my Mac so I can work at home.

--
Evan Jones: http://www.eng.uwaterloo.ca/~ejones/
"Computers are useless. They can only give answers" - Pablo Picasso

There's a couple of macosx binary packages around.

Newer one:
http://www.visionegg.org/install-macosx-details.html
older one:
http://redivi.com/~bob/



Evan Jones wrote:

> On Friday, May 9, 2003, at 12:05 Canada/Eastern, Mike C. Fletcher wrote:
>
>> The distributed wrappers should, if I'm not mistaken, be sufficient 
>> for all platforms.  There should definitely be a GLUerror present in 
>> the GLU module, the module initialization code (in the included 
>> wrappers) explicitly imports it into the module dictionary.  Have you 
>> tried doing a completely clean install?  That is, removing any 
>> previous versions, deleting the "build" subdirectory of the source 
>> tree, then building and installing?
>
>
> Yes, I have tried a completely clean install. I've even tried using 
> "python setup.py build --force" with both swig 1.3.13 and swig 1.3.16. 
> The former gives me the same error, and the latter doesn't even get as 
> far (as expected). I'm wondering if it might be a problem with Mac OS 
> X's "two level namespace" thing. I might have to investigate that.
>
>> PS: are you working with Bernie on his Pythonic VR project, or is 
>> Python just taking over the entire Waterloo campus :) .  Almost makes 
>> me want to go back.
>
>
> Actually, no, Python is just taking over. I'm taking CS488: Intro to 
> Computer Graphics this semester, and it is being converted from Tcl/Tk 
> + OpenGL to Python/Tkinter + OpenGL, and I'm trying to get the 
> environment working on my Mac so I can work at home.
>
> -- 
> Evan Jones: http://www.eng.uwaterloo.ca/~ejones/
> "Computers are useless. They can only give answers" - Pablo Picasso
>
>