Mark Hammond mhamm...@users.sourceforge.net added the comment:
Checked into trunk as r69094; merged to release26-maint as r69095, py3k
as r69096 and release30-maint as r69097.
--
resolution: accepted - fixed
status: open - closed
___
Python tracker
Martin v. Löwis mar...@v.loewis.de added the comment:
Looks fine to me, please apply.
As all the IO is done with Win32 directly, you might as well call
DeleteFile instead of remove (unless I miss something).
--
keywords: -needs review
resolution: - accepted
Mark Hammond mhamm...@users.sourceforge.net added the comment:
Ironically I just received personal mail:
I have downloaded pywin32_212 [2.6] three times today. the download
completes successfully. but on running the pywin installer i repeatedly
get an error.
Attached is a screen-shot of the
Martin v. Löwis mar...@v.loewis.de added the comment:
My apologies for not being more on top of this, but I couldn't find the
answer in the developer FAQ. This question applies to issue 4566 and
will partially apply to issue 5076. The patches are against the trunk -
after checking in, what
Mark Hammond mhamm...@users.sourceforge.net added the comment:
Thanks for the merging advice!
The patch to the build system is indeed trivial - unfortunately it also
failed to work correctly due to install.c using freopen, a CRT function,
to redirect the output. Interestingly, this probably
New submission from Mark Hammond mhamm...@users.sourceforge.net:
After consideration of issue 4120 and issue 4566, it seems to me that
executables created by bdist_wininst will have a manifest referencing
the MSVC9 assembly, and thus will be in a similar position to the .pyd
files in issue 4120
Martin v. Löwis mar...@v.loewis.de added the comment:
I think it would be even better if it didn't link with the CRT at all,
but until somebody provides a patch for that, linking statically sounds
fine to me.
--
nosy: +loewis
___
Python tracker
