Let's tackle how to locate the exact Python executable used to create a virtual environment on both platforms, while avoiding any process forking from symlinks or copied executables as you requested.

Linux Solution (Confirmed) #

As you already know, Linux virtual environments use symlinks for the python binary in the venv. Resolving this symlink directly gives you the original executable path with zero extra processes or forks:

readlink -f venv/bin/python

This command follows the symlink chain straight to the pythonXY executable that ran pythonXY -m venv venv.

Windows Solution #

Windows virtual environments don't use symlinks by default (you can enable them with --symlinks, but it's not standard), so we need alternative approaches that align with your requirement to avoid process forking. Here are two reliable methods:

Method 1: Extract from pyvenv.cfg (No Process Forking) #

You mentioned the official docs note that pyvenv.cfg contains a home key pointing to the original Python installation directory. Let's clarify why this actually fits your needs:

• The home value is the directory where the original pythonXY.exe resides. You can construct the full executable path by appending python.exe (or the versioned pythonXY.exe name) to this directory.

• To get this path without running any Python executable, use a simple command to read the file directly:

  findstr /B "home" venv\pyvenv.cfg
  

  Example output: home = C:\Python310
  The original executable would be C:\Python310\python.exe (or python310.exe if you use versioned executable names).

  This method only reads a text file—no Python processes are spawned, so there's no risk of process forking.

Method 2: Match File Version Metadata #

The python.exe in venv\Scripts is a copy of the original executable, but it retains version information that can help you trace back to the source. Use PowerShell to get the version, then cross-reference with your installed Python paths:

(Get-Item venv\Scripts\python.exe).VersionInfo.ProductVersion

Example output: 3.10.11
You can then search standard Python installation directories (like C:\Python310, C:\Program Files\Python310, or %LOCALAPPDATA%\Programs\Python\Python310) for the matching executable.

This method only inspects file metadata—no Python processes are run, so no process forking occurs.

内容的提问来源于stack exchange，提问作者Wolfgang Kuehn