py2exe and multiple PyOpenGL __init___.pyd files

Mike C. Fletcher mcfletch at rogers.com
Fri Feb 28 18:59:34 EST 2003


Not a good one at the moment.  You can see the work-around here:

    http://pyopengl.sourceforge.net/documentation/py2exe.html

You see a similar problem with PIL or any system that uses import trickery.

IMO what we need to look at doing is providing a mechanism for declaring 
redistributable sub-assemblies for packages. When a tool like py2exe 
finds a dependency it finds the associated assembly definition and says 
"oh, I'll include that assembly".  The definition can define how to 
include the assembly (e.g. copy a .zip, add extra files to the 
distribution, copy-and-rename, etceteras).  I'd like to work on that 
eventually.

HTH,
Mike

Carl Pearson wrote:

>I've run into a problem using py2exe to create a PyOpenGL executable.  
>OpenGL.GL, OpenGL.GLU and OpenGL.WGL each have a __init___.pyd file.  
>py2exe copies all the required .pyd files to the distribution directory, 
>so of course the first two __init___.pyd files get overwritten.  
>Is there a solution for this?
>  
>

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








More information about the Python-list mailing list