[Bf-committers] Meeting minutes, august 9, 2009

[Martin Poirier]

--- On Sun, 8/9/09, Ton Roosendaal <ton at blender.org> wrote:

> - Python 3.1 move: all signs are on green now; but for
> using Scons  
> building, you'll still have to keep Py 2.6 around until
> Scons also  
> migrates. This isn't so much a problem, since we'll include
> the library  
> and includes in our svn, so you don't have to install
> python 3.1.
> Campbell will remove the ugly compatibility #ifdefs
> tomorrow, be  
> warned! He'll be around in IRC to advise or help.

Here's a linux zip for py 3.1

http://blenderartists.org/~theeth/temp/python3.1.zip

It was built on linux 32 with glibc2.8 (the last one probably doesn't matter much).

As far as I know, the only architecture specific part (which would need a linux 64 counterpart) is /lib-dynload while the only platform specific stuff is in /plat-linux2

All the rest should be both platform and architecture agnostic.

Now, what we would need to do is have that zip in .blender and unzip it on startup (if not done already). The unzip is needed because python can only (IIRC) load pure py modules from zip and not dynamic binary libs. Unzipping the pure py modules is good anyway because it gives a space for pyc files and speed up module loading. We would also need to distribute the python .so lib as well as a special startup script to find it properly.

Note that we would still need a full python 3.1 install on build machines. Removing that dependency would need adding include files and prebuilt libs in /libs/linux* (I would recommend that does be optional and that the build engines uses system libs by default).

In a perfect world, these would have been solved before removing 2.6 support, but I digress.

Martin


      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com.