[Bf-committers] Moving to Python 3.2.x

[Martin Poirier]

3.2 was released two weeks ago, what's the rush to switch to it and drop 3.1?

Martin

--- On Mon, 3/7/11, Campbell Barton <ideasman42 at gmail.com> wrote:

> From: Campbell Barton <ideasman42 at gmail.com>
> Subject: [Bf-committers] Moving to Python 3.2.x
> To: "bf-blender developers" <bf-committers at blender.org>
> Received: Monday, March 7, 2011, 6:35 AM
> Now we have Mac & Windows
> building with python 3.1 we can drop support
> for all OS's.
> For Linux this probably means you'll need to build your own
> since few
> distributions support py3.2 yet.
> 
> I've updated the instructions for building python here.
> http://wiki.blender.org/index.php/Dev:2.5/Doc/Building_Blender/Linux/Troubleshooting#Python
> 
> note, since our wiki update the syntax highlighting has
> gone a strange
> (since moving servers) so some text is easier to read when
> selected.
> 
> One gotcha with 3,.2 is that python now has a suffix which
> depends on
> build-options so you may have libpython32mu.so or
> libpython32d.so,
> where before it was simply libpython32.so.
> 
> >From ./configure.in
>  * --with-pydebug (adds a 'd')
>  * --with-pymalloc (adds a 'm')
>  * --with-wide-unicode (adds a 'u')
> 
> This means getting the path to includes & libs isn't so
> simple
> anymore, for linux it may be best to search for all
> possibly
> combinations of d/m/u to detect the python version, but for
> now these
> need to be set manually.
> 
> -- 
> - Campbell
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>