[Bf-committers] Moving to Python 3.2.x
bdiego at gmail.com
Tue Mar 8 01:05:38 CET 2011
Don't take this bad, but this "python thing" is staring to be a little
annoying... yes download and build/install the new
version is just "3 command", but that is fine for one machine that is
for development.. when you have to update
a couple more of PCs that are begin used to work every day.. not
really nice (not mention the servers).
Of course you already know about this but anyway, just my two cents.
On Mon, Mar 7, 2011 at 8:35 AM, Campbell Barton <ideasman42 at gmail.com> wrote:
> 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.
> 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
More information about the Bf-committers