All right - I'm not on 2013 yet... :-/
-M
--
Martin Chatterjee
[ Freelance Technical Director ]
[ http://www.chatterjee.de ]
On Fri, Apr 20, 2012 at 4:26 PM, Helge Mathee <[email protected]> wrote:
> The code is not executed at all for me. Actually this repros on two
> machines here.
> So typing up wrong code doesn't give an error either.
>
> Regards from Sebastian Kowalski by the way. Same on his box on 2013.
>
> -H
>
>
> On 4/20/2012 14:00, Martin Chatterjee wrote:
>
> Never had that. I think there's an issue with Python's print() not
> working inside the Script Editor when using a standalone Python install
> though.
>
> Cheers, -M
> --
> Martin Chatterjee
>
> [ Freelance Technical Director ]
> [ http://www.chatterjee.de ]
>
>
>
> On Fri, Apr 20, 2012 at 2:37 PM, Stefan Kubicek <[email protected]>wrote:
>
>> Never happened to mee either, though I've been mostly using the built-in
>> Python version that ships with Softimage for some time now, which is
>> version 2.6.4. I believe to remember that this was the only
>> officially supported and working version, others have this or that issue.
>> Any particular reason you need to use 2.7.2 over 2.6.4?
>>
>> Maybe ask Steven Caron, he seems to favour 2.7.2 too (PyQt for Softimage
>> is compiled against it afaik)
>>
>>
>>
>>
>> Hey folks,
>>>
>>> I have installed 2.72 x64 as well as pywin32 for the right version.
>>> Python is showing up in the script editor as an option, python plugins
>>> work (such as custom commands and operators) but the code in the script
>>> editor itself is not executed when using python. Is this a known issue?
>>>
>>> -H
>>>
>>>
>>
>> --
>> -------------------------------------------
>> Stefan Kubicek Co-founder
>> -------------------------------------------
>> keyvis digital imagery
>> Wehrgasse 9 - Grüner Hof
>> 1050 Vienna Austria
>> Phone: +43/699/12614231
>> --- www.keyvis.at [email protected] ---
>> -- This email and its attachments are
>> --confidential and for the recipient only--
>>
>>
>
>
