One more thing.... We get the 'debugging disabled' message whenever
/anything /is run from the script editor.
-Tim
On 12/5/2012 8:01 PM, Eric Thivierge wrote:
Are you using any "print" statements instead of "LogMessage()) in your
python? I think it logs that when using that when not using the built
in Python.
--------------------------------------------
Eric Thivierge
http://www.ethivierge.com
On Thu, Dec 6, 2012 at 12:08 PM, Tim Crowson
<[email protected]
<mailto:[email protected]>> wrote:
For what it's worth, PyWin32 64-bit build 214 produces the same
end result. Soft still thinks debugging is is disabled.
-Tim
On 12/5/2012 5:45 PM, Eric Thivierge wrote:
Are you sure those are the recommended versions to be working
with? I'd check the versions that the default Softimage is using
and reflect that. Last I heard 2.7 wasn't running 100% and that
pywin32 214 was required as a bug in the version after concerning
a memory leak was yet to be fixed too. Maybe Mr. Blair has a
better idea. He's still Softimage support to me.
--------------------------------------------
Eric Thivierge
http://www.ethivierge.com
On Thu, Dec 6, 2012 at 10:16 AM, Tim Crowson
<[email protected]
<mailto:[email protected]>> wrote:
Yep, that's what I'm using. Pywin32 64-bit (in this case,
build 217, athough I see 218 is out). The installer is
"pywin32-217.win-amd64-py2.7.exe
<http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/pywin32-217.win-amd64-py2.7.exe/download>"
http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/
Again, this has been working fine on my workstation for
weeks. And we're not finding anything particularly special to
differentiate my setup from other workstations.
--
--
Signature
