[Bf-committers] Proposal for clarified VFX Reference Platform Support

Campbell Barton ideasman42 at gmail.com
Mon Jan 17 05:57:50 CET 2022

As far as I'm aware, the decision for Blender *not* to follow the VFX
platform for Python is still in place (allowing us to follow Python's
release schedule, unless there are good reasons not to).

Last time the topic came up was May 2021, the discussion petered out
and there were no conclusions from that thread or meeting minutes at
the time that any changes were planned. see: [0] "VFX reference
platform 2022 draft" thread.
Although it would have been good if the outcome of this discussion was
noted in meeting minutes (or noted needing further discussion if
developers involved thought the topic was unresolved).

My opinion on this hasn't changed from the comments made here [1].

[0]: https://lists.blender.org/pipermail/bf-committers/2021-May/thread.html#50990
[1]: https://lists.blender.org/pipermail/bf-committers/2021-May/050998.

On Sat, Jan 15, 2022 at 11:57 AM Ray Molenkamp via Bf-committers
<bf-committers at blender.org> wrote:
> All right, looks like we're tiptoeing around
> the elephant in the room, time to rip that
> Band-Aid off (feels like this metaphor kinda
> got away from me, but I'm sticking with it!)
> Let’s not beat around the bush, no-one has
> ever complained about our OIIO, Boost, VDB or
> TBB versions. People get ..passionate..
> about python, anytime someone brings up the
> VFX Platform it's python, It's never anything
> else, it's python, the rest of the VFX platform
> may as well not exist. The issue is, and will
> always be python.
> The real question is, are we going to follow
> the platform in regards to python or not.
> The way the python [1] and VFX Platforms [2]
> are released those most we'll ever have is a
> 5-month window where the two will overlap and
> there will actually be active bug fix support
> on python the python version of the VFX Platform.
> Are we OK with that?
> People get upse..uhh passionate when we "suddenly"
> change our python version. What is needed is a
> clear and decisive message regarding how we pick
> our python versions.
> Are we following:
> A) The python release schedule
> B) The VFX platform schedule
> C) Well, you know maybe, VFX kind of works out
> this year so why not, next year maybe not so
> much, we'll see, oh hey this years python has ….
> [check notes]..better….. error.. messages? we got
> to upgrade!
> D) Other
> We have been doing C, and I don't think anyone
> is super thrilled about how this is working out.
> I mostly don’t even care what we pick (not C!!)
> pick something, write it down somewhere, so people
> can rely on it.
> --Ray
> [1] https://www.python.org/dev/peps/pep-0602/
> [2] https://vfxplatform.com/about/
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> List details, subscription details or unsubscribe:
> https://lists.blender.org/mailman/listinfo/bf-committers

- Campbell

More information about the Bf-committers mailing list