I'm on Fedora 14. A quick "sudo yum update python3 --enablerepo=rawhide" updated my python to 3.2. Then just had to add SUFFIX = "mu" in my user-config.py. Pretty hacky transition for now, but it works without having to compile Py3.2 for yourself. I think most Linux distros have 3.2 in their development repository, so enabling it for updating Python should fix it.
Greets! On 03/07/2011 02:21 PM, Tobias Oelgarte wrote: > I have the same problem. Ubuntu 10.10 is still at 2.6.6 as the default. > It has 3.1 as the alternative. But why should we now need 3.2 in a rush. > This makes things only complicated for users that don't want to compile > anything on their own. > > Am 07.03.2011 14:16, schrieb [email protected]: >> Hi, >> I compile blender once o twice a week, but today I got this >> error: >> >> #error "Python versions below 3.1 are not supported anymore, >> you'll need to update your python." >> >> That keep me wondering what the >> problem was, until I realized that in blender/python/intern/bpy_util.h >> there was this check: >> >> #if PY_VERSION_HEX< 0x03020000 >> #error "Python >> versions below 3.1 are not supported anymore, you'll need to update >> your python." >> #endif >> >> Please, someone fix the message :) >> >> By the >> way, I downloaded and compiled python 3.2 and then I had to put >> BF_PYTHON_VERSION = '3.2m' in user-config.py . >> >> After that it >> copiled without problems and runned. I haven't tested blender yet to >> find if this breaks anything. >> >> >> >> ----Mensaje original---- >> De: >> [email protected] >> Fecha: 07/03/2011 12:35 >> Para: "bf-blender >> developers"<[email protected]> >> Asunto: [Bf-committers] Moving >> to Python 3.2.x >> >> 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. >> > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
