I've tryed to install mod_wsgi using pip lately in a venv. This installation process fails with a message about a missing venv\scripts\libs\python38.lib file as reported in https://github.com/GrahamDumpleton/mod_wsgi/issues/506

It seems that this file used to be included in virtual environments but the behaviour has changed. This library seems to be a dependency for some modules, shouldn't it be included in the virtual environment? Is this behaviour change desired? If so, how should modules link to python.lib?

Thanks in advance

When have you seen this work previously? On my Windows 10 machine there is no Scripts\libs directory for Python 3.7, let alone a python37.lib file in any directory that I can find.

The python38.lib file isn't present in any venv, whether created by virtualenv or "python -m venv". I believe the mod_wsgi build process may not cater for building in a venv on Windows.

When created with "python -m venv", a venv contains the file pyvenv.cfg with contents like this:

home = C:\Users\Vinay\AppData\Local\Programs\Python\Python38
include-system-site-packages = false
version = 3.8.1

and the location of python38.lib on this system is given by the libs directory relative to the home value in the above snippet.

I don't think this is a venv bug so I will probably close this issue soon, unless you provide more evidence of an actual problem in the venv package.

If that is the intended way to proceed then I will patch mod_wsgi.

Sorry for the inconvenience and thank you very much for the pointers.

Thanks!