How to Check Your Python Version

Why checking the Python version matters

Knowing which Python interpreter and version you are running is foundational for reproducible development, dependency compatibility, and security. Projects often declare minimum or exact version requirements, and tooling such as linters, type checkers, and virtual environments behave differently across versions. This guide explains enduring, cross platform methods to verify your Python version in shells, scripts, and automated workflows, with distinctions between the python and python3 commands and how to inspect executable paths and build metadata.

Preferred command line checks

Use these commands in your terminal or command prompt to obtain reliable version information. Each approach emphasizes clarity and portability so you can rely the results across common environments.

Standard version flag

The most widely supported way to check Python version is the --version flag. It outputs a concise line with the major, minor, and patch level, and works for both python and python3 where either executable is available.

• python --version
• python3 --version

Interactive version query

You can also query the version from within the Python REPL or from an executed one liner. The sys module exposes version and version_info for programmatic use, and platform provides a related version string on some platforms.

• python -c "import sys; print(sys.version)"
• python -c "import sys; print(sys.version_info)"

Inspecting the interpreter executable

When multiple Python installations coexist, it is helpful to confirm which binary is invoked and where it resides. Combining version output with executable resolution reduces ambiguity in scripts and tooling configuration.

Which and type lookups

On Unix like systems, use shell builtins to locate the interpreter that would run if you typed python or python3 in your current environment.

• which python or which python3
• type python or type python3

Readlink resolution for symlinks

In environments where the executable is a symlink, chaining readlink calls can reveal the ultimate target path, which is valuable when debugging virtual environment linkage or custom installations.

• readlink -f $(which python3)

Cross platform considerations: python vs python3

Command and executable naming varies by operating system and distribution conventions. Understanding these patterns helps you choose the right invocation and avoid ambiguous references.

Naming patterns at a glance

Programmatic checks inside Python code

When you need the version from within a script, library, or CI step, importing the standard library is the most stable approach. The examples below emphasize immutable attributes and avoid reliance on external processes.

Using the sys module

The sys module is always available in standard Python and exposes version components as named attributes, suitable for runtime checks or logging.

import sys
print(sys.version)
print(sys.version_info)

Using the platform module

The platform module provides complementary release and version helpers, which can be useful for broader environment introspection beyond just Python.

import platform
print(platform.python_version())
print(platform.python_version_tuple())

Distinguishing version types

sys.version returns a string with version, build number, compiler, and build date in a single line. sys.version_info returns a named tuple that is ideal for conditional checks, while platform.python_version() returns a clean dotted string suitable for display or comparison.

Managing multiple installations and virtual environments

In practice, developers often juggle multiple Python releases, per project virtual environments, and system packages. Consistent checks reduce confusion about which interpreter is active.

Virtual environment indicators

When a virtual environment is activated, the prompt usually changes to show the environment name, and the executable path points into the environment directory. You can still run python --version to confirm the interpreter linked to that environment.

Verifying paths and site packages

Use the sysconfig or site modules to inspect where Python is reading site packages and installing third party libraries. This helps confirm that the checked interpreter matches the expected environment.

import sysconfig
print(sysconfig.get_path('purelib'))

Troubleshooting common mismatches

Commands may appear to hang, return exit codes indicating errors, or show unexpected paths. Aligning your invocation with your intent avoids subtle configuration issues.

When python and python3 differ

On some systems, python still maps to Python 2, while python3 points to Python 3. Using the explicit python3 command removes ambiguity. On modern distributions and on Windows, python often defaults to Python 3, but it is best to verify.

Exit codes and silent failures

A return code of zero typically indicates success, while a nonzero code can signal invocation errors or missing modules when using scripted checks. Always validate command output when integrating version checks into automation.

Summary of methods and when to use them

For quick interactive checks, the version flag is fastest. For scripts and automation, prefer the standard library to avoid spawning subprocesses. In complex setups, combine executable resolution with version queries to ensure correctness.

Quick reference table

Related topics

After confirming your interpreter version, you may want to manage dependencies, linting, and testing across different Python releases using tools such as pip, virtual environments, and CI pipelines. Consistent version checks integrate cleanly into those workflows and support long term maintenance.