Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Zach is waiting to see how this impacts folks on the OIIO side
Possibly looking into GitHub actions / secrets to auto-commit stub updates
Need to talk with the CI working group etc about it
generates static analysis in IDEs, potentially helps LLM analysis of code / generation of code
Kevin - what’s the point of committing it to the repo? could it just be a part of the wheel build process?
Zach - there’s a reason, I think it’s to do with lack of support in earlier python versions
Fine with user needing to update manually, but need checks in place to make sure they are up to date before release / wheel generation
#2056 - if the fix is small, let’s just get the fix in for this format and then go from there. Get Remi and Mark Boorer’s eyes back on this and go from there. We should also add tests.
#1984 - tag for 2.6.0, it’s an API change
#1931 - ocioarchive enhancements
Used internally at framestore
Enables archive resolving environment/context variables vs. maintaining them
Should minimal set and resolving of context or not be two separate options?
Needs API changes, so another one for 2.6
#1909 - if anyone has time to review and validate, that would be good.
PIE code executables - probably needs re-worked given we’re now on more modern cmake versions - Kevin will take a look
#1794 - old, likely should close
Kevin - we did end up doing something like this in the OCIO ACES 2 implementation - but that is very specific and not general, and doesn’t mean this is a good addition generally
#1739 - ctest to pytest - too much overhead for devs, should close
Last minute note on ocioview - looks like it requires pytest. This resulted in a discussion around whether or not we move ocioview to its own repo so its dependencies are not linked to OCIO the library. Seems logical. Discuss with Thomas and group next time.