>> Why not just require virtualenv (Python 3 comes with the venv module >> built-in and doesn’t need anything else), > > I know you are a BIG fan of Python 3, but not everybody has it as the > default…
I meant requiring virtualenv for Python 2 and using venv in Python 3. >> 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? > > This obviously needs internet connection, right? What I want is a > separation between setting up the environment and calling the Makefile > – the latter should work offline, too. In that case, how about punting on the issue entirely and instead publishing docwriter on PyPI and letting people pip it from there? You just test for its availability in PATH and tell people what to do to get it otherwise. Then you have full control over whether you want to install it globally, in your user dir or in a venv. _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
