Bug report
Bug description:
Dear Python Core Development Team,
I am writing to you today for a detailed observation regarding the installation and module resolution process for Python 3.14.x versions on Windows. My experience, consistently observed across Python 3.14.4, 3.14.5, and 3.14.6, points to a potential area for enhancement that could significantly benefit the developer community, especially those new to Python.
Observed Behavior & Core Issue:
Upon installing Python via the official Windows installer (e.g., into C:\Program Files\Python314), I noted that the pip package manager tends to install packages into the user-specific directory (%APPDATA%\Python\Python314\site-packages). The critical challenge arises because the primary Python interpreter, residing in the system-wide Program Files location, does not seem to automatically incorporate this user site-packages path into its default module search sequence.
Impact and Troubleshooting Experience:
This lack of automatic path synchronization directly resulted in persistent ModuleNotFoundError exceptions when executing scripts that relied on packages installed via pip. To elaborate on the challenges encountered:
Initial Installation vs. Execution: While pip install <package> reported successful installation into the user’s AppData directory, subsequent attempts to import <package> within scripts executed by the Program Files Python interpreter would fail.
Extensive Troubleshooting: Resolving this issue required considerable effort, including:
Performing multiple clean reinstalls of Python 3.14.x.
Systematically clearing previously installed user packages.
Carefully adjusting system environment variables (PATH, PYTHONPATH).
Utilizing explicit --user flags with pip, which often yielded the “Defaulting to user installation because normal site-packages is not writeable” message, yet the fundamental import problem persisted.
Workaround Implementation: Ultimately, I was able to establish a functional environment by employing advanced workarounds. This involved executing both python and pip commands using their absolute paths (e.g., "C:\Program Files\Python314\python.exe" -m pip install ...) and ensuring a strict adherence to these explicit pathways. This process was significantly aided by leveraging AI tools like ChatGPT-5.5 to better understand and navigate the system’s configuration intricacies.
Suggestion for Improvement:
While I appreciate the flexibility Python offers across diverse environments, I believe addressing this path synchronization discrepancy on Windows could greatly improve the user experience. Ensuring that the system-installed Python interpreter seamlessly recognizes packages installed in the user’s site-packages directory by default would:
Reduce setup friction for new developers.
Minimize troubleshooting time for common import errors.
Streamline the overall development workflow.
I kindly request that the development team consider investigating and potentially enhancing the installer’s logic or Python’s environment discovery mechanisms to ensure better out-of-the-box coherence between pip’s default installation location and the interpreter’s module search path on Windows.
Thank you for your time and for considering this feedback. Your dedication to making Python an excellent development tool is greatly valued.
Sincerely,
A Python user from Iran
CPython versions tested on:
3.14
Operating systems tested on:
No response
Bug report
Bug description:
Dear Python Core Development Team,
I am writing to you today for a detailed observation regarding the installation and module resolution process for Python 3.14.x versions on Windows. My experience, consistently observed across Python 3.14.4, 3.14.5, and 3.14.6, points to a potential area for enhancement that could significantly benefit the developer community, especially those new to Python.
Observed Behavior & Core Issue:
Upon installing Python via the official Windows installer (e.g., into C:\Program Files\Python314), I noted that the pip package manager tends to install packages into the user-specific directory (%APPDATA%\Python\Python314\site-packages). The critical challenge arises because the primary Python interpreter, residing in the system-wide Program Files location, does not seem to automatically incorporate this user site-packages path into its default module search sequence.
Impact and Troubleshooting Experience:
This lack of automatic path synchronization directly resulted in persistent ModuleNotFoundError exceptions when executing scripts that relied on packages installed via pip. To elaborate on the challenges encountered:
Suggestion for Improvement:
While I appreciate the flexibility Python offers across diverse environments, I believe addressing this path synchronization discrepancy on Windows could greatly improve the user experience. Ensuring that the system-installed Python interpreter seamlessly recognizes packages installed in the user’s site-packages directory by default would:
I kindly request that the development team consider investigating and potentially enhancing the installer’s logic or Python’s environment discovery mechanisms to ensure better out-of-the-box coherence between pip’s default installation location and the interpreter’s module search path on Windows.
Thank you for your time and for considering this feedback. Your dedication to making Python an excellent development tool is greatly valued.
Sincerely,
A Python user from Iran
CPython versions tested on:
3.14
Operating systems tested on:
No response