Python version

New releases and general discussions.

Post » Wed Feb 25, 2009 11:33 am

[quote="Someone on python.org":30ngo7rj]Python 3.0 final was released on December 3rd, 2008.

Python 3.0 (a.k.a. "Python 3000" or "Py3k") is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Also, the standard library has been reorganized in a few prominent places.[/quote:30ngo7rj]
What, if any, is Construct's schedule for switching to Python 3? Is it more of a "We'll worry about it when Construct is more mature" or "we need python module X, and can't switch before the module does"?

(Just curious. I don't speak python, but that makes it all the more interesting whether there's a point to diving into version 2 at this stage.)
B
2
S
1
G
4
Posts: 60
Reputation: 1,320

Post » Wed Feb 25, 2009 11:39 am

We've neglected Python a little for a fair few builds, but honestly, we want to see it as good as possible for 1.0. 0.99 should fix it up. I'll talk to David now about using 3.0.
B
3
S
2
G
5
Posts: 1,777
Reputation: 5,529

Post » Wed Feb 25, 2009 11:55 am

Interesting question, as the current build's python is broke, and has been that way for some time.
So falling back to the old standard of "if it ain't broke, don't fix it" really doesn't apply here.

On the other hand will the next version of Python offer the same functionality? Probably... eventually, but starting out a lot of the modules that were available for the old version wont be backwards compatible.

This is actually an issue that many programs that use scripting are finding these days, for example Blender use's an older version of python, but the develops won't upgrade for the fact that existing scripts made will be broke in a new version. Personally I've had this same issue with Gimp, as new versions come out, the very scripting language created for it is changed, breaking existing scripts, loosing functionality.
Image Image
B
161
S
48
G
90
Posts: 7,347
Reputation: 66,749

Post » Wed Feb 25, 2009 12:00 pm

It's a semi-advantage Python isn't well adopted yet by Construct users, as we can update to 3.0 and make some changes to the way we use it (behaviors, effects etc).

It isn't broken per-se, but to use it you have to install Python yourself, which is obviously annoying.
B
3
S
2
G
5
Posts: 1,777
Reputation: 5,529


Return to Construct Classic Discussion

Who is online

Users browsing this forum: No registered users and 3 guests