Minigame is probably never going to support Python 3.
Here's the relevant bit of the devlog :
diana_coman I would have to look into 2.78a to see what they claim to do there and whether any of it might help with the cal3d export part; basically from a strictly Blender point of view I worked with a whole set of versions from 2.4 to 2.7 and I would say 2.67 is fine in there; what you might want to test first however before choosing one version is how the different exporters behave if you want to try use/adapt an existing exporter. Basically different exporters work to different degrees with different versions - making it all a huge headache; cutting this short I would rather just stick to 2.71 and develop an exporter for that (it has a baking API which I'm not sure is in 2.67 as well). For fuck's sake they list "Python APIs changes" as FEATURE, arrgh.
mircea_popescu Heh. Are they on 3.x yet ?
diana_coman I think latest Blender shouts for Python 3 ONLY, yeah.
mircea_popescu Heh. I'm not terribly sure Python 3 has any sort of future. It seems altogether unable to muster specific support in TMSR, and the Open Sores movement is running out of steam.
shinohai I still prefer 2.7 to be honest.
mircea_popescu actually their statement is so lulzy it's worth quoting.
Short version: Python 2.x is legacy, Python 3.x is the present and future of the language
Python 3.0 was released in 2008. The final 2.x version 2.7 release came out in mid-2010, with a statement of extended support for this end-of-life release. The 2.x branch will see no new major releases after that. 3.x is under active development and has already seen over five years of stable releases, including version 3.3 in 2012, 3.4 in 2014, and 3.5 in 2015. This means that all recent standard library improvements, for example, are only available by default in Python 3.x.
Guido van Rossum (the original creator of the Python language) decided to clean up Python 2.x properly, with less regard for backwards compatibility than is the case for new releases in the 2.x range. The most drastic improvement is the better Unicode support (with all text strings being Unicode by default) as well as saner bytes/Unicode separation.
Besides, several aspects of the core language (such as print and exec being statements, integers using floor division) have been adjusted to be easier for newcomers to learn
So basically, "it is the present (delusionally) and future (hopefully) of the language because it has more Unicode crapi and it's easier for noobies." Good luck have fun, if your focus is new people that means you're an altcoin and get lostii. Meanwhile 2 branch is FINALLY stable. I have no fucking idea what they must be drinking to imagine "more releases" is a selling point, but whatever it is, they're guzzling it down.
diana_coman Several aspects of the core language (such as print and exec being statements, integers using floor division) have been adjusted to be easier for newcomers to learn " <- eurgh, so now core aspects are decided based on what is "easy" for newcomers, way to go. Guess that might be a cutting point re Blender versions then. Basically whatever Blender version is the last to work on Python 2.x and we'll make it work with that - it's anyway more reasonable than to import whatever new python mess.
mircea_popescu Pretty much. I can't imagine better news than "we finally took the creative gnats away, branch is finally stable". Hallelujah.
This discussion covers in-house software, yes, but not legacy software. On the contrary, it's the development plan for the future, a future which very pointedly leaves no space for Python 3. Discuss.
———It should probably be noted that Unicode support is not seriously entertained by the Republic, which means that it isn't the future of anything. [↩]Elitism means something. [↩]
« The conundrums of the contemporaneous financier
Unicode is fucking stupid - the definitive article. »
Category: Meta psihoza
Monday, 28 November, Year 8 d.Tr.