We didn't go with 2.7 because it used pywin 214 which was buggy.
Not sure if 215 is any better (I'm trying to find the bug numbers).
2.7 does show up as an available scripting language (on Windows).
The bug that was in 214 is still Open, so I assume it is still in 215.
It's a mem leak in the Application object that causes other problems too, iirc.
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Stephen Blair
Sent: February-22-11 12:09 PM
To: soft...@listproc.autodesk.com
Softimage ships with 2.6.4 (on Windows).
We didn't go with 2.7 because it used pywin 214 which was buggy.
Not sure if 215 is any better (I'm trying to find the bug numbers).
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Martin Chatterjee
Sent: March-29-12 6:19 AM
To: soft...@listproc.autodesk.com
Subject: Re: Official Supported version of Python for SI?
On Tue, Feb 22, 2011 at 6:09 PM, Stephen Blair <Stephe...@autodesk.com<mailto:Stephe...@autodesk.com>> wrote:
Softimage ships with 2.6.4 (on Windows).
We didn't go with 2.7 because it used pywin 214 which was buggy.
Not sure if 215 is any better (I'm trying to find the bug numbers).
Hi Stephen, hi everybody,
I'd be very interested to know if that bug that made you stay with pywin 214 back then is fixed in the current pywin 217 version.
Of course I'm happy to check the pywin changelogs myself - but I would need a bit more details about the issue that you encountered back then.
Thanks in advance,
Martin
--
Martin Chatterjee
[ Freelance Technical Director ]
[ http://www.chatterjee.de<http://www.chatterjee.de/> ]