# Virtual env PATH question **URL:** \ **Category:** Python Help\ **Created:** [October 24, 2026, 10:00pm UTC](https://discuss.python.org/t/virtual-env-path-question/109654 "2026-10-24T22:00:21Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![petersuter](https://avatars.discourse-cdn.com/v4/letter/p/13edae/32.png) [@petersuter](https://discuss.python.org/u/petersuter)\ **Post date:** [October 25, 2026, 8:07am UTC](https://discuss.python.org/t/virtual-env-path-question/109654/3 "2026-10-25T08:07:23Z")
> [@Making venvs relocatable friendly](https://discuss.python.org/t/making-venvs-relocatable-friendly/96177/): > > Hi all, In short: Have resolution of paths in pyvenv.cfg be relative to the pyvenv.cfg file. Why? This allows a venv to be relocatable enough that the basic Python bootstrapping process gets far enough to hand over execution to application code that can handle the rest. (Spoiler: this is actually possible today! But is brittle and relies on some specific code paths being taken). By having a well-defined location (the pyvenv.cfg location) that paths are relative to, it allows constructing the s… > [@Q: What stops a venv from being relocatable?](https://discuss.python.org/t/q-what-stops-a-venv-from-being-relocatable/57166): > > After re-reading Brett’s [excellent blog about how virtual environments work](https://snarky.ca/how-virtual-environments-work/), I’ve been wondering something. If a venv is just: 3 directories (bin, include, lib/pythonX.Y/site-packages) Optional lib64 symlink Then is the only reason that venv aren’t relocatable due to the shebangs with absolute urls in the “bin” folder? These shebangs help to “autoactivate” the Python interpreter to pickup site-packages? If my understanding is correct, and I don’t need any console scripts in “bin”, does that… --- _[View the full topic](https://discuss.python.org/t/virtual-env-path-question/109654)._