As a reminder for those who don't 'watch' the OIIO GitHub page and therefore don't get the automatic emails with every pull request...
In the master branch, over the past few months we have completely overhauled the Python bindings. They were previously pretty broken, or at least neglected for some time, but now are completely first-class citizens: they've been thoroughly scrubbed, fixed where broken, augmented where they fell behind C++, amended for missing sections (like ImageBufAlgo!), fully documented, and have extensive unit tests to ensure that they don't accidentally break. Additionally, now that I understand boost::python, I can ensure that any new features or API modifications on the C++ side are simultaneously and correctly updated on the Python side. So, anyway, if you were one of the many people interested in Python bindings over the years only to find them inadequate, please give them a try in master. In addition to the PDF documentation, the testsuite/*/test*.py unit tests are pretty good examples of the Python bindings in action. Within the next few days, I will branch to create a 1.3 release. For a couple weeks following that, we'll designate it as a "beta", which gives us a little wiggle room to modify the APIs. So if you are interested in Python, please do check it out within that period and be on the lookout for anything I've done wrong or clumsily (I still don't consider myself an expert Python programmer and may have done things strangely). The beta period is our chance to make changes before we declare 1.3 a "stable release" and lock the APIs. And if anybody has any other high-priority requests that will necessitate changing the API (including non-Python matters), please bring it to my attention ASAP if you want it to make it into 1.3. -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
