Thread: [PyOpenGL-Devel] Support for the new numpy
Brought to you by:
mcfletch
From: Bill B. <wb...@gm...> - 2006-07-05 06:25:01
|
PyOpenGL currently has support for Numeric 2.3. The last version of Numeric was 2.4, but even that has been superceded by Numpy (which basically began with the Numeric 2.4 code base). Numpy is currently at version 0.9.8but should hit the 1.0 release this summer. There will be no further development on Numeric, from what I understand. So is there any plan to update PyOpenGL to work with the new Numpy? The upgrade is supposed to be pretty easy to do, mostly consisting of replacing the #include for numeric's C api with the #include for numpy's. So I might be willing to volunteer if no one else is interested. In particular I'm interested in using PyOpenGL with wxPython and Numpy on Win32. --Bill |
From: Mark H. <ma...@mi...> - 2006-07-06 16:24:13
|
The ctypes version (CVS only) of PyOpenGL supports Numpy; as I've read here and elsewhere the plan is to roll it out w/ Python 2.5 and official inclusion of ctypes. http://pyopengl.cvs.sourceforge.net/pyopengl/OpenGL-ctypes/ Mark Bill Baxter wrote: > PyOpenGL currently has support for Numeric 2.3. The last version of > Numeric was 2.4, but even that has been superceded by Numpy (which > basically > began with the Numeric 2.4 code base). Numpy is currently at version > 0.9.8but should hit the > 1.0 release this summer. There will be no further development on > Numeric, > from what I understand. > > So is there any plan to update PyOpenGL to work with the new Numpy? > > The upgrade is supposed to be pretty easy to do, mostly consisting of > replacing the #include for numeric's C api with the #include for numpy's. > So I might be willing to volunteer if no one else is interested. > > In particular I'm interested in using PyOpenGL with wxPython and Numpy on > Win32. > > --Bill > > ------------------------------------------------------------------------ > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ------------------------------------------------------------------------ > > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Devel mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-devel > |
From: Andrew S. <str...@as...> - 2006-07-06 17:27:35
|
There are comments indicating that the numpy header files cannot be found. Here's the standard idiom to find them: *import* numpy my_ext = Extension(my_extension_name,my_sources,include_dirs = [numpy.get_numpy_include()]+my_include_dirs) I hope it helps! Andrew Mark Heslep wrote: >The ctypes version (CVS only) of PyOpenGL supports Numpy; as I've read >here and elsewhere the plan is to roll it out w/ Python 2.5 and official >inclusion of ctypes. > >http://pyopengl.cvs.sourceforge.net/pyopengl/OpenGL-ctypes/ > > >Mark > > >Bill Baxter wrote: > > >>PyOpenGL currently has support for Numeric 2.3. The last version of >>Numeric was 2.4, but even that has been superceded by Numpy (which >>basically >>began with the Numeric 2.4 code base). Numpy is currently at version >>0.9.8but should hit the >>1.0 release this summer. There will be no further development on >>Numeric, >>from what I understand. >> >>So is there any plan to update PyOpenGL to work with the new Numpy? >> >>The upgrade is supposed to be pretty easy to do, mostly consisting of >>replacing the #include for numeric's C api with the #include for numpy's. >>So I might be willing to volunteer if no one else is interested. >> >>In particular I'm interested in using PyOpenGL with wxPython and Numpy on >>Win32. >> >>--Bill >> >>------------------------------------------------------------------------ >> >>Using Tomcat but need to do more? Need to support web services, security? >>Get stuff done quickly with pre-integrated technology to make your job easier >>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>------------------------------------------------------------------------ >> >>_______________________________________________ >>PyOpenGL Homepage >>http://pyopengl.sourceforge.net >>_______________________________________________ >>PyOpenGL-Devel mailing list >>PyO...@li... >>https://lists.sourceforge.net/lists/listinfo/pyopengl-devel >> >> >> > > >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >PyOpenGL Homepage >http://pyopengl.sourceforge.net >_______________________________________________ >PyOpenGL-Devel mailing list >PyO...@li... >https://lists.sourceforge.net/lists/listinfo/pyopengl-devel > > |
From: Andrew S. <str...@as...> - 2006-07-06 17:54:40
|
Andrew Straw wrote: >There are comments indicating that the numpy header files cannot be >found. Here's the standard idiom to find them: > >*import* numpy >my_ext = Extension(my_extension_name,my_sources,include_dirs = >[numpy.get_numpy_include()]+my_include_dirs) > > Hmm, thunderbird cleverly put asterisks around 'import' when I cut and pasted it from another source... Obviously that's not part of the standard idiom... |
From: Mike C. F. <mcf...@vr...> - 2006-07-06 21:28:37
|
Andrew Straw wrote: > Andrew Straw wrote: > > >> There are comments indicating that the numpy header files cannot be >> found. Here's the standard idiom to find them: >> >> *import* numpy >> my_ext = Extension(my_extension_name,my_sources,include_dirs = >> [numpy.get_numpy_include()]+my_include_dirs) >> Cool. We actually don't need the headers for numpy any more, as it now supports the __array_*__ protocol. Basically we can use that to retrieve the data-pointer from the array without the need for any C or mucking about with calculating offsets for each Numpy and Python combination. Will file it away for future reference, however. Have fun, Mike -- ________________________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com |