Last weekend I started to tinker with pybind11 (https://github.com/pybind/pybind11), which is very similar to Boost.Python, but header-only, allegedly builds MUCH faster, and by starting with C++11 as a baseline, its use and implementation are a lot simpler.
I got partially done with converting the oiio python bindings to it, and am liking the direction it was going, so I'll probably finish it. But an issue has come up that I'm seeking feedback on. For actual blocks of pixels, like the results of ImageInput.read_image(), it seems that it's a lot more straightforward to pass back and forth NumPy arrays rather than old style python arrays. So... 1. Does anybody object to that? Is NumPy already deep enough in your Python practice that you would accept (and maybe prefer) switching to directly using numpy arrays to pass image data around? 2. If so, would you prefer that it hand you a true multidimensional array organized like [y][x][channel]? Or would you rather just get a flat 1D array with all the values, and you can cast it to the array shape that you prefer? -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
