Hey Allen, Not sure if this is one any help but I’m maintaining a Mac 3rdparty build with OIIO and most of the dependencies: https://github.com/mikaelsundell/3rdparty <https://github.com/mikaelsundell/3rdparty>
For all builds I stick to a single python version to avoid version conflicts and other problems: https://github.com/mikaelsundell/3rdparty/blob/master/CMakeLists.txt:227 <https://github.com/mikaelsundell/3rdparty/blob/master/CMakeLists.txt:227> Homebrew is easier to manage but from time to time it can be nice to be in full control of the stack, Mikael Mikael Sundell mikael.sund...@gmail.com > On 21 Jan 2023, at 01:00, Allen Hemberger <al...@allenhemberger.com> wrote: > > Hi there; > > Emailing developer lists is terrifying to me. But, I have a question about > managing OIIO on my MacBook (M1): > > At the moment, I install OIIO via Homebrew. I’m not married to this method, > it’s just a thing that worked for me, and a method I saw mentioned on the > Github docs. Homebrew installs a particular version of oiio, which comes with > its own particular version of Python bindings. I haven’t quite figured out > whether I can download python bindings specifically for a particular python > version. > > I’m somewhat code-y, and I move amongst python versions frequently. I use > pyenv to manage my various python environments on my Mac, which seems to work > fairly well (definitely easier than using Homebrew to manage python > versions). > > It’s often the case that I ‘upgrade’ my Homebrew setup, which refreshes oiio, > which gets me a new python bindings, often built against a particular version > of python which I may or may not already have installed. > > The most recent oiio home-brew update, for example, offers python bindings > for 3.11. I haven’t yet needed to move anything else to 3.11, I’m still on > 3.10. Is there a way for me to ‘get’ oiio python bindings for 3.10? Or do I > have to upgrade Python to keep it in sync with whatever the Homebrew version > of oiio decides to give me? I find the need to ‘chase’ the Homebrew python > bindings a little difficult, as it of course means I need to re-set up all my > python modules and so on. > > The whole experience makes me think there might be a more graceful way for me > to manage this, and I went looking on Github to see if anyone else might have > already asked this question. I couldn’t find anything suggesting as much, but > did find this email list, so thought I’d ask here. > > I would ideally like my oiio bindings to ‘follow’ my python version, rather > than the other way around. Or, I might imagine Homebrew would install > bindings for multiple minor versions of Python (e.g. 3.9, 3.10, 3.11) rather > than just a single version, to allow for some amount of flexibility in dev > environments…though I realize this is a Brew thought, not an OIIO thought... > > Anyway, I’m hoping someone could offer some wisdom about managing this > better. Please be gentle, I know a medium amount about managing development > environments on Apple silicon, but have much to learn. > > Many thanks; > —allen > > > _______________________________________________ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
