[Bf-committers] Moving to Python-3.8

Ray Molenkamp ray at lazydodo.com
Fri Nov 8 15:43:30 CET 2019

On 2019-11-08 1:37 a.m., dr. Sybren A. Stüvel wrote:

> Are there any concrete reasons we stick to those particular versions? Or
> is it just a matter of someone taking the time to update them?

I don't think we have official rules about this but
the un-official one I have been using for years is:

Module owners what rely on a dependency can integrate
newer versions and ask for an update of a dep once they
are done on bf-c and the platform devs will take care
of the rest. Previous examples [1][2][3]

That being said the integration *has* to be done by the
module teams, the platform devs just don't/can't know
every single implementation detail of the 30-40 deps we
rely on.

Sometimes we get patches that include lib building
support (like embree) which is appreciated but by no means
required, odds are the platform devs for a platform
are better and quicker at scripting deps than a dev
that has never developed on said platform.

So the barrier for lib updates is a low as I can make it
all you have to do is test the new version works, and ask.

Given we are formalizing lots of things, perhaps now
that module teams are more established we should
assign responsibly for the deps they require to them?


[1] https://lists.blender.org/pipermail/bf-committers/2018-December/049691.html
[2] https://lists.blender.org/pipermail/bf-committers/2019-June/050006.html
[3] https://lists.blender.org/pipermail/bf-committers/2019-August/050119.html

More information about the Bf-committers mailing list