I've got a Windows 7 environment where I need to develop a Python Windows Service using Python 3.4. I'm using pywin32's win32service module to setup the service and most of the hooks seem to be working ok.
The problem is when I attempt to run the service from source code (using python service.py install
followed by python service.py start
). This uses PythonService.exe to host service.py - but I'm using a venv virtual environment and the script can't find it's modules (error message discovered with python service.py debug
).
Pywin32 is installed in the virtualenv and in looking at the source code of PythonService.exe, it dynamically links in Python34.dll, imports my service.py and invokes it.
How can I get PythonService.exe to use my virtualenv when running my service.py?
Thanks very much for posting this question and a solution. I took a slightly different approach which might also be useful. It is pretty difficult to find working tips for Python services, let alone doing it with a virtualenv. Anyway...
This is using Windows 7 x64, Python 3.5.1 x64, pywin32-220 (or pypiwin32-219).
C:\Python35\python -m venv myvenv
call myvenv\scripts\activate.bat
pip install pypiwin32
, pip install path\to\pywin32.whl
python myvenv\Scripts\pywin32_postinstall.py -install
.
C:\Windows\System32
. The DLL's are named pythoncom35.dll
and pywintypes35.dll
. So virtual environments on the same machine on the same major Python point release will share these... it's a minor tradeoff :)myvenv\Lib\site-packages\win32\pythonservice.exe
to myvenv\Scripts\pythonservice.exe
_exe_path_
to point to this relocated exe. This will become the service binPath. For example: _exe_path_ = os.path.join(*[os.environ['VIRTUAL_ENV'], 'Scripts', 'pythonservice.exe'])
.I think why this works is that Python looks upwards to figure out where the Libs folders are and based on that sets package import paths, similar to the accepted answer. When pythonservice.exe is in the original location, that doesn't seem to work smoothly.
It also resolves DLL linking problems (discoverable with depends.exe from http://www.dependencywalker.com/). Without the DLL business sorted out, it won't be possible to import from the *.pyd files from venv\Lib\site-packages\win32
as modules in your scripts. For example it's needed allow import servicemanager
; as servicemanager.pyd
is not in the package as a .py file, and has some cool Windows Event Log capabilities.
One of the problems I had with the accepted answer is that I couldn't figure out how to get it to accurately pick up on package.egg-link paths that are created when using setup.py develop
. These .egg-link files include the path to the package when it's not located in the virtualenv under myvenv\Lib\site-packages
.
If it all went smoothly, it should be possible to install, start and test the example win32 service (from an Admin prompt in the activated virtualenv):
python venv\Lib\site-packages\win32\Demos\service\pipeTestService.py install
python venv\Lib\site-packages\win32\Demos\service\pipeTestService.py start
python venv\Lib\site-packages\win32\Demos\service\pipeTestServiceClient.py
Another important note in all this is that the service will execute the python code in a completely separate environment to the one you might run python myservice.py debug
. So for example os.environ['VIRTUAL_ENV']
will be empty when running the service. This can be handled by either:
os.environ
.