python-poetry / python-poetry/poetry
Allow configuration of the in-project virtual env directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.5k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
- 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
When setting virtualenvs.in-project to true, poetry creates ".venv" directory in the project directory.
When creating in Pycharm a virtual environment for a project, a "venv" directory is created.
It will be very useful if both tools can share the same directory.
To allow this I suggest introducing a new configuration variable called virtualenvs.in-project-venv-name that will be used wherever ".venv" is currently used. The default value for this variable will be ".venv", of course. However, the user will be able to modify it (e.g. to "venv") if necessary.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Poetry's handling of the virtualenvs.in-project setting and the code that creates or references the .venv directory. Implement the configurable name while preserving .venv as the default, then verify that a custom name such as venv is used consistently and allows sharing with PyCharm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100