As part of getting PyQt working on multiple workstations, one of the
prerequisites (as far as we can tell) is to have PyWin32 installed to
our local Python on our C:\ drive. So we've done that on a few systems
and are hitting a snag.
1) The PyWin installer, on finishing, spits out this error, but
otherwise appears to install ok:
/close failed in file object destructor://
//sys.excepthook is missing//
//lost sys.stderr/
2) Thereafter, if Softimage is using the Windows Python, all outputs to
the Softimage Python console spit out an additional output:
/Debugging interfaces not available - debugging is disabled..
/
3) I found this article
<http://blog.naver.com/PostView.nhn?blogId=ojwhan&logNo=30001471029&parentCategoryNo=3&categoryNo=&viewDate=&isShowPopularPosts=false&from=postView>
from years ago explaining that a custom command to 'import
win32traceutil' will solve the problem. So I tried that. But it solves
the problem only for error outputs. Standard messages are not logged at
all. Meaning I can't use 'print' and have to use
'Application.LogMessage()' instead.
I'm not even sure if the PyWin installer error is related or not. It
certainly seems that way, since the error pertains to the sys.stderr
stream. But even after stripping and re-installing PyWin32 on MY
machine, and getting that same error, my Softimage does not give me any
"/debugging is disabled.." /errors. That's only on my machine though. 4
other systems today have all behaved the same way, resulting in the
'debugging is disabled' message. And we can't tell that there's anything
really different with my system, except that I'm the only one not on
Windows 7 SP1.
I'm a bit over my head with this. My questions to list are:
1) What's going on here?
2) Is there a way to avoid using PyWin in order to use PyQt in Softimage
(building PyQt against 2.6.4 not being an option, or at least, not
desirable)
3) What are the implications if we continue with the self-installing
command to import win32traceutil and not having a 'print' option, or
seemingly any sys.stdout messages? In practice so far, I've only ever
needed that for printing data, since errors get output in the sys.stderr
stream, and that part is working fine. Just seems wrong not have the
sys.stdout stream working correctly...
--
Signature
*Tim Crowson
*/Lead CG Artist/
*Magnetic Dreams Animation Studio, Inc.
*2525 Lebanon Pike, Building C. Nashville, TN 37214
*Ph* 615.885.6801 | *Fax* 615.889.4768 | www.magneticdreams.com
[email protected]
