Why not just require virtualenv (Python 3 comes with the venv module built-in 
and doesn’t need anything else), automatically make a virtual environment in 
the working directory (pip should be installed automatically in it and if not, 
a call to `python -m ensurepip` in the venv fixes that) and use it from the 
Makefile? Would save the user a lot of hassle. Stuff inside the venv (at least 
with the venvs created by Py3’s venv) can be directly called like 
`venv/bin/python -m …` or `.\venv\Scripts\python -m …` without activation.
_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to