A Python virtual environment is not a complete, self-contained Python installation—and it is not necessarily made mostly of symlinks. It has its own configuration, executable entry, scripts, and package-installation directory, but normally reuses the base Python installation’s standard library. The executable may be copied or symlinked depending on platform, build, and options; that distinction does not determine where packages are installed.
Is a Python venv just a symlink?
No. A venv is a directory-based environment with its own pyvenv.cfg, interpreter entry, scripts, and site-packages location. The interpreter entry can be a copy or a symlink, but the environment’s package area and configuration are distinct either way.
Python’s Python 3.14 venv documentation describes the executable as a copy or symlink as appropriate for the platform or creation options. On POSIX systems, the executable directory is conventionally bin; on Windows, it is Scripts. A typical environment also has a platform-appropriate site-packages directory.
So “mostly a symlink” is a misleading shorthand: it treats one part of the layout—the interpreter entry—as if it described the whole environment.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
What the venv shares with base Python—and what it keeps separate
When Python starts, it looks for pyvenv.cfg near the executable. Its home setting identifies the base Python location. Python then reports the environment path as sys.prefix and the base installation path as sys.base_prefix. This startup behavior and the separation between prefixes are described in PEP 405.
The base installation normally supplies the standard library and headers, while package installation locations use the environment prefix. That means a venv can have its own installed third-party packages without containing another complete copy of Python’s standard library.
By default, packages in the base installation’s system site-packages are not available to the venv. Creating it with --system-site-packages opts into making those packages available. This changes package visibility; it does not turn the venv into a standalone Python distribution.
Copies, symlinks, and platform differences
The venv options request behavior rather than guaranteeing an identical layout on every machine. The Python documentation describes --symlinks as asking for symlinks where they are not the platform default, and --copies as asking for copies where symlinks are the default. Platform and build details still matter.
| Case | What to expect |
|---|---|
| POSIX | The executable directory is conventionally bin. The interpreter entry may be copied or symlinked according to the platform and creation options. Python 3.14 documentation |
| Windows | The executable directory is conventionally Scripts. Symlinks are supported but not recommended by the Python documentation; opening python.exe by double-clicking it in File Explorer can resolve the symlink eagerly and ignore the virtual environment. Python 3.14 documentation |
| macOS framework builds | PEP 405 explains that the framework build’s stub executable must be copied rather than symlinked. This is the PEP’s design rationale, not a complete inventory of current Python distributions. PEP 405 |
PEP 405 also discusses historical Windows constraints: symlink creation has had inconsistent support and may require administrator permissions. For non-system-wide installations, DLL and extension-module files may also need copies or symlinks so Python can find them. These details are further reasons not to assume every venv has the same files or that its executable is the only platform-dependent piece.
Activation is optional
Activation is a convenience that adjusts PATH so commands such as python resolve to the environment. It is not what makes the environment isolated, and you can skip activation by invoking its interpreter directly:
- POSIX:
.venv/bin/python - Windows:
.venvScriptspython.exe
Because activation sets the VIRTUAL_ENV variable, it can be tempting to use that variable to detect whether Python is running in a venv. But it is not a reliable test: direct invocation does not require activation. The Python documentation instead describes checking whether sys.prefix differs from sys.base_prefix.
What this means when you create or move an environment
Create it where you plan to use it
Make an environment with python -m venv .venv. Use --copies if copies suit your needs, but a copied executable does not make the environment independent of the base installation. The environment still uses the base Python’s standard library under the documented layout.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do not treat it as portable
Python’s documentation says environments are generally not movable or copyable. Installed scripts can contain an absolute path to the environment’s interpreter, so copying the directory to another location can leave those scripts pointing at the old path. Instead, recreate the venv at its destination and reinstall dependencies from a requirements file or lock file.
After upgrading Python
If Python has been upgraded in place, venv provides an --upgrade option for updating an existing environment to use that installation. That is different from relocating the environment: for a move, recreate it at the destination.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
