On Thu, Apr 16, 2015 at 9:58 AM, Paul Moore <p.f.mo...@gmail.com> wrote:
> On 16 April 2015 at 14:43, Kevin Horn <kevin.h...@gmail.com> wrote: > > Those that want to use pywin32 in a virtualenv (or just without all the > > system changes) could simply install the wheel (or even an sdist, > perhaps) > > from the command line using pip, and then perform whatever other steps > they > > want manually. > > Just as a data point, converting the existing wininst installer for > pywin32 to a wheel (using wheel convert), and installing that via pip, > is entirely workable (for the win32api/win32file type basic > functionality). The pypiwin32 project (started by Glyph as a way of > providing pywin32 wheels from PyPI) includes wheels for Python 3.x > which I built that way, so it's certainly seen some level of use. > > The wheels are probably unnecessarily big, as they'll include all of > pythonwin, and the ActiveX Scripting and service creation support, > which I guess won't work in that configuration, but they are a good > starting point for checking precisely what will work unmodified from a > wheel. > For people interested in a lightweight alternative to pywin32, we have the pywin32ctypes project, which started as a way to get access to win32 credentials without depending on DLL (to avoid file locking issues with inplace updates). The project is on github (https://github.com/enthought/pywin32-ctypes), and is already used by a few projects. We support both cffi and ctypes backends (the former to work out of the box on cpython, the latter to work on pypy). David
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
