[Bf-committers] Moving to Python-3.8

Damien Coureau damien.coureau at ubisoft.com
Thu Nov 7 16:51:33 CET 2019

I wouldn't advise on overlooking the VFX Platform.

The "joke" does not come from there but from Autodesk and The Foundry.
The VFX Platform is actually trying to cope with it in a realist way and slowly push everyone to the tip of progress.

Writing pipeline tools compatible between 3.* is not an issue, it's about having extensions working in all the toolset without recompiling and deploying them for each DCC.
If we diverge from the VFX Platform, we will lose this advantage and some industry adoption.

I don’t mean we can't, but it should be for a good reason (or optional)

But more importantly:
One of the major improvement in 2.8 was that we could import python extensions from PyPI.
Let me stress out how this is a *major vital feature* for any small/middle sized animation/VFX studio.
If we choose to overlook the VFX Platform and jump to 3.8, we must be sure to keep Blender's python interpretor compatible with the official extensions (PyPI).

IMHO of course 😊


-----Message d'origine-----
De : Bf-committers <bf-committers-bounces at blender.org> De la part de Toni Alatalo
Envoyé : mercredi 6 novembre 2019 16:07
À : bf-blender developers <bf-committers at blender.org>
Objet : Re: [Bf-committers] Moving to Python-3.8

Native code Python modules, I mean typically C written libs or APIs like Blender's, used to not be compatible between Python releases.

However, there seems to be a part of the ABI that remains compatible between releases, since 3.2:


I don't know whether and how exactly people may mix native modules in and out of Blender in Python VFX pipelines.

But just a note that it may be less a problem now than earlier. Or not, I didn't check how useful the compatible part of the binary interface is.

2 cently, Toni

On Wed, 6 Nov 2019, 12:31 Bastien Montagne, <montagne29 at wanadoo.fr> wrote:

> TL;DR Am all for switching to python 3.8 in Blender 2.82.
> TBH I would not be too much concerned about that VFX reference thing, 
> waiting over ten years until a deprecated technology is finally 
> officially not supported anymore to switch to a new, modern one sounds 
> like a joke to me, especially in an industry that is always supposed 
> to be at the tip of progress in techs!
> And as Sybren said, py3.8 will support all of py3.7 features, so just 
> write your code for 3.7 if you really want to stick to that 'industry 
> standard' thing.
> Bastien
> On 05/11/2019 22:33, dr. Sybren A. Stüvel wrote:
> > On 05/11/2019 21:31, Luciano A. Muñoz Sessarego wrote:
> >> I honestly would stick to the VFX reference one, yesterday daniel 
> >> bysted made a point about it on twitter:
> >> https://twitter.com/3DBystedt/status/1191527352012070912
> > It looks like his point was that things are easier now that the VFX 
> > Reference Platform is no longer on an ancient version of Python.
> >
> > Compared to supporting Python 2 and 3 in one script (which is also 
> > doable, but not fun), it'll be peanuts to just write pipeline tools 
> > for Python 3.7 and have them run on 3.8 as well.
> >
> > Sybren
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
Bf-committers mailing list
Bf-committers at blender.org

More information about the Bf-committers mailing list