I ran across this problem myself awhile back, and it seems to be
common enough that they added a feature to distutils to handle it.
I have added a copy of my setup.cfg to CVS, which contains:
[build]
force=1
[bdist_wininst]
user_access_control=auto
With "force=1", it should theoretically clean o
The Python 3.2 32-bit build was the only one affected and I've uploaded
a 216.1 build for this version only. It is identical to the 216 builds
except for the build ID and the conversion of all files to py3k syntax.
What went wrong? I was incorrect the other day about the 32bit and
64bit vers
Tim Golden wrote:
"""
Re: [python-win32] Possible trouble with pywin23-216 on python 3.2
"""
Aha! There's your problem: you're trying to install pywin23.
Unless of course you're using one of those rare machines based
on Intel's little-known
Smarta
(err) (umm)
Thanks Tim, I'll try that.
--
Vernon
On Mar 3, 2011 1:50 AM, "Tim Golden" wrote:
> """
> Re: [python-win32] Possible trouble with pywin23-216 on python 3.2
> """
>
> Aha! There's your problem: you're t
"""
Re: [python-win32] Possible trouble with pywin23-216 on python 3.2
"""
Aha! There's your problem: you're trying to install pywin23.
Don't know why you didn't spot it yourself... ;)
TJG
___
pyth
On 3/03/2011 4:15 PM, Vernon Cole wrote:
Attempting to install using the binary installer, the installer gets to
"postinstall script finished", but the display window says:
v v v v v v v v
Copied pythoncom32.dll to C:\Windows\system32\pythoncom32.dll
Copied pythoncomloader32.dll to C:\Windows\sys
Attempting to install using the binary installer, the installer gets to
"postinstall script finished", but the display window says:
v v v v v v v v
Copied pythoncom32.dll to C:\Windows\system32\pythoncom32.dll
Copied pythoncomloader32.dll to C:\Windows\system32\pythoncomloader32.dll
Copied pywintyp
