In README, under the section titled "development environment", we state that virtualenv is recommended. But what we really assume there is that virtualenvwrapper is installed (that is where mkvirtualenv and workon commands come from), not just virtualenv.
Installing and using virtualenvwrapper requires additional steps, and some knowledge of the tool. This is fine. However, Python 3 also ships a built-in venv module which seems to work just fine with FIM. We can use venv like so:
(Older versions of pip and setuptools that gets shipped with Python may not always work; which is why pip install --upgrade pip setuptools is a good idea.)
It would be useful to update the README. We could:
Recommend one or both of virtualenvwrapper and venv.
Add a link to virtualenvwrapper PyPI project, if that is still recommended.
Add instructions for using venv, if using venv is acceptable.
ibaldin
commented
1 year ago
In README, under the section titled "development environment", we state that
virtualenvis recommended. But what we really assume there is that virtualenvwrapper is installed (that is wheremkvirtualenvandworkoncommands come from), not just virtualenv.Installing and using virtualenvwrapper requires additional steps, and some knowledge of the tool. This is fine. However, Python 3 also ships a built-in venv module which seems to work just fine with FIM. We can use venv like so:
(Older versions of pip and setuptools that gets shipped with Python may not always work; which is why
pip install --upgrade pip setuptoolsis a good idea.)It would be useful to update the README. We could:
venv, if usingvenvis acceptable.