{"id":57504,"date":"2026-09-30T20:47:50","date_gmt":"2026-09-30T20:47:50","guid":{"rendered":"https:\/\/www.askpython.com\/?p=57504"},"modified":"2026-09-30T20:47:51","modified_gmt":"2026-09-30T20:47:51","slug":"find-where-python-is-installed","status":"publish","type":"post","link":"https:\/\/www.askpython.com\/python\/examples\/find-where-python-is-installed","title":{"rendered":"Where Is Python Installed? Find Its Path"},"content":{"rendered":"\n\n

An IDE can run Python even when `where.exe python` returns no match in a separate shell. I\u2019m intrigued that a blank lookup can coexist with a running interpreter.<\/p>\n\n\n\n

You can get the runtime path from the environment that launches your program. The first distinction is between a command your shell can find and the executable reported by the running process.<\/p>\n\n\n\n

Which Python path are you trying to find?<\/h2>\n\n\n\n

A shell lookup answers which command your terminal can start. Inside a running Python process, sys.executable<\/a> reports the executable path.<\/p>\n\n\n\n

An environment manager or integrated development environment (IDE) may choose a runtime separately from the shell, so check the environment that launches your program.<\/p>\n\n\n\n

Homebrew documents its prefixes. Other installers can place Python in different directories.<\/p>\n\n\n\n

The executable path names a file. An installation prefix is a directory, so the two values answer different questions.<\/p>\n\n\n\n

Question<\/th>Check<\/th>What it tells you<\/th><\/tr><\/thead>
Which executable runs this Python process?<\/td>sys.executable<\/td>The interpreter path for the current process<\/td><\/tr>
Which command can this shell start?<\/td>Windows or Unix-like shell lookup<\/td>One or more shell-resolved candidates<\/td><\/tr>
Which environment is active?<\/td>sys.prefix and sys.base_prefix<\/td>The active environment prefix and base prefix<\/td><\/tr>
Where are Python libraries installed?<\/td>python3 -m site<\/td>The site directories used by that interpreter<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Start from the environment that runs your code<\/h2>\n\n\n\n

Run the check from the same terminal or environment that starts your program. A separate terminal can resolve a different Python command.<\/p>\n\n\n\n

    \n
  1. Open the terminal or IDE environment used to launch the program.<\/li>\n\n\n
  2. If you use a virtual environment or Conda environment, activate or select it first.<\/li>\n\n\n
  3. Use the command name your program uses, such as python on Windows or python3 in a macOS or Linux shell.<\/li>\n<\/ol>\n\n\n\n

    An IDE may select its interpreter in project settings, so a check in its integrated console is more useful than a lookup in an unrelated shell.<\/p>\n\n\n\n

    The shell resolves names such as python and python3 through PATH. This environment variable tells the shell which directories to search, and activating an environment can change the result.<\/p>\n\n\n\n

    Print the executable Python is running<\/h2>\n\n\n\n

    Use the same Python command that runs your script. In Windows Command Prompt or PowerShell, use python.<\/p>\n\n\n

    \npython -c "import sys; print(sys.executable)"\n<\/pre><\/div>\n\n\n
    In a macOS or Linux shell, use python3 to ask the running process for its executable path.<\/p>\n\n\n
    \npython3 -c 'import sys; print(sys.executable)'\n<\/pre><\/div>\n\n\n
    \"Terminal
    sys.executable prints the executable selected for the Python process running this command.<\/figcaption><\/figure>\n\n\n\n
    Use the printed path when a tool asks you to select the same Python runtime. Python’s sys documentation describes sys.executable as the executable for the running interpreter.<\/p>\n\n\n\n
    Find commands your shell can start<\/h2>\n\n\n\n
    The prompt’s command lookup and a running process can refer to different interpreters, so use the check that matches your task.<\/p>\n\n\n\n
    Windows Command Prompt and PowerShell<\/h3>\n\n\n\n
    In Command Prompt, use the Windows where utility to search the current directory and PATH for matching command files.<\/p>\n\n\n
    \nwhere.exe python\n<\/pre><\/div>\n\n\n
    where.exe searches the current directory and PATH. Its output lists matching files from those search locations.<\/p>\n\n\n\n
    In PowerShell, Get-Command can list every command named python and show its command type and source. Check the type before treating a result as an executable file.<\/p>\n\n\n
    \nGet-Command python -All | Select-Object CommandType, Name, Source\n<\/pre><\/div>\n\n\n
    Microsoft documents where.exe<\/a> as searching the current directory and PATH for matching files. PowerShell’s Get-Command reference<\/a> covers aliases and functions, along with scripts and applications, so its output can include more than executable files.<\/p>\n\n\n\n
    Check CommandType before using Source as an executable path, because Alias and Function entries describe PowerShell commands.<\/p>\n\n\n\n
    macOS and Linux shells<\/h3>\n\n\n\n
    In Bash or Zsh, type -a lists matching command names. The Portable Operating System Interface (POSIX)<\/a> specifies that command -v reports how the shell interprets one name.<\/p>\n\n\n
    \ntype -a python3\ncommand -v python3\n<\/pre><\/div>\n\n\n