Change default to `virtualenvs.in-project = true`
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
The config virtualenvs.in-project
should be defaulted to true at installation. Personally, I did this almost every single time.
On my local, codespaces, and many dockerfiles are set POETRY_VIRTUALENVS_IN_PROJECT=true
. If the 80% always changes it every single time, why don’t we consider make it a new default.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Configuration | Documentation | Poetry - Python dependency ...
Create the virtualenv inside the project's root directory. If not set explicitly, poetry by default will create virtual environment under {cache-dir}/ ...
Read more >Poetry: How to keep using the old virtual environment when ...
If set to true , the virtualenv wil [sic] be created and expected in a folder named .venv within the root directory of...
Read more >Python Virtual Environments: A Primer
With the default settings, venv will install both pip and setuptools. Using pip is the recommended way to install packages in Python, ...
Read more >venv — Creation of virtual environments — Python 3.11.1 ...
Changed in version 3.4: Installs pip by default, added the --without-pip and --copies ... set to true if venv is run with the...
Read more >Python Virtual Environments tutorial using Virtualenv and Poetry
Say you're on two projects, two of them are using serpapi library ... you need to set Python System Interpreter back to the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can honestly live with either but I do have a preference for in-project venvs as it is much less surprising for developers that are new to Python, or just developers that are new to
poetry
. It also mimics other similar tools in Python (tox) and in the SW community (npm
, etc…)As long we can switch between them I think the question really is “who is the default for”? Is it “for users who don’t want to configure anything”? In that case the answer should coincide with what most users do Is it “for developers who don’t yet understand the intricacies”? In that case the answer should coincide with what they would expect. etc…
Hi, is this issue going to be resolved somehow? I personally also vote in favour of default in-project virtualenv which I consider more convenient.