|
From: SourceForge.net <no...@so...> - 2011-09-08 00:47:42
|
Bugs item #3402824, was opened at 2011-09-02 06:44 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3402824&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Bryan Cook (cookbr) Assigned to: Nobody/Anonymous (nobody) Summary: Windows Installer: close failed in file object destructor Initial Comment: When running through pywin32-216.win-amd64-py2.7.exe on Windows Server 2008 R2, I got the following message on the 'Finish' screen of the Installation Wizard ... close failed in file object destructor: sys.excepthook is missing lost sys.stderr ... does this negatively impact the installation at all? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2011-09-08 10:47 Message: There is another open bug on this, so I'm closing this as a duplicate. To ensure the post install process completes, you can just run "python scripts\pywin32_postinstall.py -install" at any time. Also, the change you mention should be the fix for this problem - it is just that a new release is yet to be made with that patch in place. ---------------------------------------------------------------------- Comment By: Enrico Tröger (eht16) Date: 2011-09-08 01:46 Message: We got the same problem here. Some more details: - Windows 2008 R2 Datacenter SP1 - Python 2.7.2 64bit - PyWin32 pywin32-216.win-amd64-py2.7.exe What we also noticed: - in the Datacenter edition with SP1 it works as user, even with admin privileges but it won't work when installed as the user Administrator (i.e. showing the error messages in the OP's report) - it worked in Windows Server 2008 R2 Standard even as user Administrator Could the fix in [1] be related to this problem? [1] http://pywin32.hg.sourceforge.net/hgweb/pywin32/pywin32/rev/a64d8ac23e61 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3402824&group_id=78018 |
