Some programs (ex. Emacs with auto-virtualenvwrapper package) uses .venv file to auto-determine the virtualenv of the project. Which is pretty handy. As well as, it doesn't make sense inside a poetry to try to set the venv, when it is a file.
| Name |
Last commit
|
Last Update |
|---|---|---|
| .github | Loading commit data... | |
| assets | Loading commit data... | |
| docs | Loading commit data... | |
| poetry | Loading commit data... | |
| tests | Loading commit data... | |
| .appveyor.yml | Loading commit data... | |
| .coveragerc | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .pre-commit-config.yaml | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| Makefile | Loading commit data... | |
| README.md | Loading commit data... | |
| get-poetry.py | Loading commit data... | |
| make-linux-release.sh | Loading commit data... | |
| poetry.lock | Loading commit data... | |
| pyproject.toml | Loading commit data... | |
| sonnet | Loading commit data... | |
| tox.ini | Loading commit data... |