Yeah, certainly if there are multiple versions of Python installed, setting PYTHON_VERSION at build time seems to help it out.
It seems to work for me, able to get it all working for Python3 at least in the current master (at least, with some patches I have pending, hope to get out today). I don't know if I want to backport it to 1.8, because 1.9 changed a lot about how the python bindings work. I'm expecting to branch a new release beta on 1 Oct, so maybe let's just allow that to be the version where python3 is definitely fully working. > On Sep 24, 2018, at 9:13 AM, Richard Shaw <[email protected]> wrote: > > Just and FYI, but as of F30 (future release) all Python2 modules are being > obsoleted to stay ahead of the 2020 EOL for Python2. > > I have built a Python3 version of the module but has to specify > PYTHON_VERSION to CMake. > > Anything I need to worry about? > > Thanks, > Richard > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
