Python 3.2

[joepal]

Just a head's up for the future, seems http://developers.slashdot.org/story/11 ... 2-Released python 3.2 has been released.

The reason this is important is that it marks the end of both backwards-porting of feature to the 2.x branches, as well as guarranteed source backwards compatibility. (the latter is my interpretation of the pages linked from the article above, I might have understood wrong).

Since debian squeeze was just released with python 2.6.6 as default python, I guess all debian derivates (such as ubuntu) will support 2.x for at least two more years, but we're seeing the end of its expected lifetime here.

[Manuel]

Hi Joel, thanks.
The plans are to concentrate all efforts in order to reach 1.0 "final" very quickly (I mean, add all base features), and then work on the porting for 3.x
Best,

Manuel

[ThomasL]

The most common difference between 2.x and 3.x is that print is a function rather than an operator. It is of course not the most significant difference, but it caused by far most errors when I switched from Blender 2.4x and 2.5x.

This statement causes an error in 3.x:

Code: Select all

print foo, bar, baz

This statement works in both 2.x and 3.x, but the output looks bad in 2.x:

Code: Select all

print(foo, bar, baz)

This works and looks good in both 2.x and 3.x.

Code: Select all

print("%s %s %s" % (foo, bar, baz))

By using the third form one can reduce the work when it is time to port.

[Manuel]

This works and looks good in both 2.x and 3.x.

Code: Select all

print("%s %s %s" % (foo, bar, baz))

By using the third form one can reduce the work when it is time to port.

Ok, thanks.
Yes, we have to code in a 3.x oriented perspective.

Best,

Manuel