[Bf-committers] Upgrading to Python 3.3.2
sergey.vfx at gmail.com
Mon Oct 21 12:35:55 CEST 2013
Every update on the release build environment is pretty much dangerous.
Linker things are breaking pretty much easy.
I'm fine with updating py to 3.2.2 after today's release, but would suggest
make no changes to release builders now.
On Mon, Oct 21, 2013 at 11:46 AM, Bastien Montagne <montagne29 at wanadoo.fr>wrote:
> Eh, I thought we already were on py3.3.2 (installdeps is , at least)? I
> mean, mini-updates of python are bug-fixes only, so we should always
> use the latest, imho? But indeed svn libs are older (we even still have
> some py3.2!)… Not to be done before 2.69 is released, for sure! ;)
> And py3.4 is coming soon now (as in, early 2014), with at least one
> important bugfix for us (standardio encoding on Windows), and perhaps
> too that enum stuff we may find uses to. ;)
> Le lun. 21 oct. 2013 11:30:58 CEST, Alex Fraser a écrit :
> > Hi all,
> > I'd like to propose an upgrade for Python to version 3.3.2. The
> > current version (3.3.0) seems to have a bug that triggers in the game
> > engine when loading a second or third game file . This may be
> > system-specific: it doesn't happen on my computer, but it does happen
> > on a friend's, with the same executable. Please see the bug report for
> > details.
> > Does anyone object to upgrading to Py 3.3.2?
> > Cheers,
> > Alex
> > 
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
With best regards, Sergey Sharybin
More information about the Bf-committers