On Wed, Mar 9, 2011 at 11:59 AM, Dave Plater wrote:
> On 03/09/2011 10:11 AM, Campbell Barton wrote:
>> On Wed, Mar 9, 2011 at 7:07 AM, Dave Plater wrote:
>>
>>> On 03/09/2011 05:24 AM, Campbell Barton wrote:
>>>
Only supporting a single version of python IMHO is important to reduce
ove
On 03/09/2011 10:11 AM, Campbell Barton wrote:
> On Wed, Mar 9, 2011 at 7:07 AM, Dave Plater wrote:
>
>> On 03/09/2011 05:24 AM, Campbell Barton wrote:
>>
>>> Only supporting a single version of python IMHO is important to reduce
>>> overhead with a small developer team,
>>>
>>>
>>
On Wed, Mar 9, 2011 at 7:07 AM, Dave Plater wrote:
> On 03/09/2011 05:24 AM, Campbell Barton wrote:
>> Only supporting a single version of python IMHO is important to reduce
>> overhead with a small developer team,
>>
> I'm still in the dark as to why external system python which is
> maintained b
On 03/09/2011 05:24 AM, Campbell Barton wrote:
> Only supporting a single version of python IMHO is important to reduce
> overhead with a small developer team,
>
I'm still in the dark as to why external system python which is
maintained by the distro python maintainer has to be 3.2 for blender t
On Wed, Mar 9, 2011 at 4:15 AM, Martin Poirier wrote:
>
>
> --- On Tue, 3/8/11, Campbell Barton wrote:
>
>> As said before in the last mail, its fairly arbitrary when
>> we upgrade.
>> But I'd really not want to have to worry about maintaining
>> 2 versions
>> of python for more then a months, tw
--- On Tue, 3/8/11, Campbell Barton wrote:
> As said before in the last mail, its fairly arbitrary when
> we upgrade.
> But I'd really not want to have to worry about maintaining
> 2 versions
> of python for more then a months, two months at most.
You're saying that like we HAD to support Py 3
Hi,
Let be a little clear here, we are not talking about support 2, 3,
4... N versions of python at the same time, we talk about
have a little of consideration before the update.
I am not again update to 3.2, 3.3 or 5.5, but yes about update to a
new version with only 2/3 week just because we wan
On Wed, Mar 9, 2011 at 1:45 AM, Richard Shaw wrote:
> On Tue, Mar 8, 2011 at 6:13 PM, Campbell Barton wrote:
>> We can upgrade python without causing too much inconvenience just be
>> ensuring we document how to install the latest python.
>> I thought that documenting how to build python would be
On Tue, Mar 8, 2011 at 6:13 PM, Campbell Barton wrote:
> We can upgrade python without causing too much inconvenience just be
> ensuring we document how to install the latest python.
> I thought that documenting how to build python would be enough, but it
> seems us bearded linux geeks who like to
On Tue, Mar 8, 2011 at 11:25 PM, Matt Ebb wrote:
> On Wed, Mar 9, 2011 at 10:00 AM, Martin Poirier wrote:
>>
>> Unless the benefits outweighs the hindrances, there's nothing lost by
>> waiting until the next minor release.
>
> This sounds sensible to me. Considering the widespread inconvenience
On Tue, Mar 8, 2011 at 11:00 PM, Martin Poirier wrote:
>
>
> --- On Mon, 3/7/11, Campbell Barton wrote:
>
>> Python do a new releases fairly in-frequently, I recall
>> when we first
>> moved to Py3.1 (dropping 2.x) there were hardly any
>> packages in
>> distros and most Linux devs needed to buil
On Wed, Mar 9, 2011 at 10:00 AM, Martin Poirier wrote:
>
> Unless the benefits outweighs the hindrances, there's nothing lost by waiting
> until the next minor release.
This sounds sensible to me. Considering the widespread inconvenience
caused by these sorts of things, it would seem that unless
--- On Tue, 3/8/11, Ton Roosendaal wrote:
> Which also brings me to the point that for Linux only Ken
> Hughes is on
> the maintainer list mentioned. Might be good to add at
> least 1 or 2
> names who should at least be involved with decisions like
> this?
I can certainly help with that (a
--- On Mon, 3/7/11, Campbell Barton wrote:
> Python do a new releases fairly in-frequently, I recall
> when we first
> moved to Py3.1 (dropping 2.x) there were hardly any
> packages in
> distros and most Linux devs needed to build,
> though I expect we have a lot more people building blender
>
On 03/08/2011 11:39 AM, Ton Roosendaal wrote:
> Hi,
>
> It's also my fault, I slipped making minutes of meeting 9 days ago,
> and forgot to include the py 3.2 topic in last meeting's notes. The
> issue was extensively discussed in irc for 1 or 2 weeks though. The
> windows/osx platform mainta
Hi,
It's also my fault, I slipped making minutes of meeting 9 days ago,
and forgot to include the py 3.2 topic in last meeting's notes. The
issue was extensively discussed in irc for 1 or 2 weeks though. The
windows/osx platform maintainers checked on it, and when all went
smooth for these
@Martin, no this wasn't discussed at the meeting, once we had other
platforms supported Ton was ok for me with the decision.
@Diego, yep, was aware I'd get some complaints, but for updates on
non-development systems couldn't they use build made elsewhere with
py3.2 bundled?.
Python do a new rele
Hi,
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..
On 03/07/2011 01:35 PM, Campbell Barton wrote:
> 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.
>
This rpm macro gets
On Monday 07 March 2011, Domino Marama wrote:
> the trick with python is to use "sudo make altinstall" so it goes
> in /usr/local and doesn't overwrite the standard python.
> just add
> BF_PYTHON = '/usr/local'
> BF_PYTHON_VERSION = '3.2m'
> to your user_config.py and do
> ln
> -s /usr/local/lib
Sorry for the mess of my last message, these web mail clientes
In
ubuntu natty (11.04) python 3.2 will be the version used for python3,
as you can see here:
http://packages.ubuntu.com/natty/python3
So I
don't think It would be a problem for the next ubuntu version, just:
apt-get install
t. (as had hapened
to me) :)
Mensaje original
De: ideasma...@gmail.com
Fecha:
07/03/2011 15:34
Para: "bf-blender developers"
Asunto: Re: [Bf-committers] Moving to Python 3.2.x
Reasons to
move to 3.2 sooner then later:
*note* with the original switch to py3.1
we agreed to bu
es).
Martin
--- On Mon, 3/7/11, Campbell Barton wrote:
> From: Campbell Barton
> Subject: Re: [Bf-committers] Moving to Python 3.2.x
> To: "bf-blender developers"
> Received: Monday, March 7, 2011, 9:34 AM
> Reasons to move to 3.2 sooner then
> later:
> *n
On Mon, 2011-03-07 at 14:43 +0100, Tobias Oelgarte wrote:
> That may work for Fedora. But i could not find any packages for Ubuntu
> 10.10 so far. So i will need to compile python on my own and make a mess
> out of my system again...
I've updated the documentation on how I build Blender with Col
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.
gt;>> 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
>>>>>>>
t;>>>>>>> anything on their own.
>>>>>>>>
>>>>>>>> Am 07.03.2011 14:16, schrieb rsaave...@ono.com:
>>>>>>>>> Hi,
>>>>>>>>> I compile blender once o twice a week, but today I got
gt;>>>> 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,
>>
ng what the
>>>>>>> problem was, until I realized that in
>>>>>>> blender/python/intern/bpy_util.h
>>>>>>> there was this check:
>>>>>>>
>>>>>>> #if PY_VERSION_HEX< 0x0302
>>>>>&g
alized 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 n
0x0302
>>>>> #error "Python
>>>>> versions below 3.1 are not supported anymore, you'll need to update
>>>>> your python."
>>>>> #endif
>>>>>
>>>>> Please, someone fix the message :)
>&
>>>> #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 .
&g
>>> 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 tes
e 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'
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 origi
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:
> ideasma...@gmail.com
> Fecha: 07/03/2011 12:35
> Para: "bf-blender
> developers"
> Asunto: [Bf-committers] Moving
> to Python 3.2.x
>
> Now we have Mac& Windows building with python 3.1 we
> can drop suppor
ned. I haven't tested blender yet to
> find if this breaks anything.
>
>
>
> ----Mensaje original----
> De:
> ideasma...@gmail.com
> Fecha: 07/03/2011 12:35
> Para: "bf-blender
> developers"
> Asunto: [Bf-committers] Moving
> to Python 3.2
F_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:
ideasma...@gmail.com
Fecha: 07/03/2011 12:35
Para: "bf-blender
developers"
Asunto
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 wrote:
> From: Campbell Barton
> Subject: [Bf-committers] Moving to Python 3.2.x
> To: "bf-blender developers"
> Received: Monday, March 7, 2011
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
41 matches
Mail list logo
