# X-post: discussions around standardizing local/workspace virtual environment naming

**URL:** <https://discuss.python.org/t/x-post-discussions-around-standardizing-local-workspace-virtual-environment-naming/23263>\
**Category:** Developer Tools\
**Created:** [January 28, 2023, 11:25pm UTC](https://discuss.python.org/t/x-post-discussions-around-standardizing-local-workspace-virtual-environment-naming/23263 "2023-01-28T23:25:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [January 28, 2023, 11:25pm UTC](https://discuss.python.org/t/x-post-discussions-around-standardizing-local-workspace-virtual-environment-naming/23263/1 "2023-01-28T23:25:19Z")

</div>

For those that don’t follow the [Packaging - Discussions on Python.org](https://discuss.python.org/c/packaging/14) category here, there’s some discussions around virtual environments which may interest/impact those of us who try to integrate with virtual environments.

[PEP 704 - Require virtual environments by default for package installers](https://discuss.python.org/t/pep-704-require-virtual-environments-by-default-for-package-installers/22846/) proposes making `.venv` the name to use when you create a virtual environment in your workspace with your code.

[https://discuss.python.org/t/setting-up-some-guidelines-around-discovering-finding-naming-virtual-environments/](https://discuss.python.org/t/setting-up-some-guidelines-around-discovering-finding-naming-virtual-environments/) is me trying to see if a `.venv` file that acts somewhat like a virtual environment-specific symlink solution is a good idea.