(original) (raw)

It's likely that they're using the broken version of bdist\_wininst for their installer (I thought Mark reported the issue and had a workaround though...). It's already fixed, but hasn't been released yet.

Another workaround is to use "wheel convert" on the exe and then install the wheel. You miss out on their post-install steps, but most people don't need those anyway.

Cheers,
Steve

Top-posted from my Windows Phone

From: Burkhard Meier
Sent: ‎12/‎28/‎2016 1:43
To: Glenn Linderman
Cc: Python Dev
Subject: Re: \[Python-Dev\] PEP 514 and pywin32

Try the 'gohlke' download site. Whenever getting stuck in some of the newest Python 3.x versions, that side usually has installers that work. It did work for me just now, using Python 3.6.0 64-bit on Windows 10 64-bit OS.

Burkhard

On Tue, Dec 27, 2016 at 9:17 PM, Glenn Linderman <glenn@nevcal.com> wrote:

So today I tried to install pywin32 on my new Python 3.6.0 and got the following error:

\---------------------------
Cannot install
\---------------------------
Python version 3.6-32 required, which was not found in the registry.
\---------------------------
OK
\---------------------------

Seems like pywin32, although built for 3.6, doesn't understand or conform to the PEP 514? So the installer doesn't work? I suspect maybe the code would still work, if it would install. I also noted that pip cannot find a compatible pywin32, and PyPI only reports compatibility through Python 3.3.

1\. Where should this be reported? SourceForge?
2\. Anyone know a workaround?

--
Glenn

Experience is that marvelous thing that enables you to recognize a
mistake when you make it again. -- Franklin Jones

_______________________________________________

Python-Dev mailing list

Python-Dev@python.org

https://mail.python.org/mailman/listinfo/python-dev

Unsubscribe: https://mail.python.org/mailman/options/python-dev/burkhardameier%40gmail.com