This document summarizes the Discourse thread to identify gaps in Python distribution.
Generally, the consensus has been-
- Installers are useful. This is due to ease of use and lack of trust in third-party distributions.
- Relocatable unzip-and-run distributions would be useful
- Relocatable Python using unzip-and-run distributions. The build should be explicitly tagged.
- Script wrappers generated by pip are an issue with relocatable installs on Windows. Managing user expectations regarding unzipped build vs installer is also an issue.
- Making python-build-standalone available on python.org
- Distributing a snap/flatpak similar to the Microsoft store distribution
- Managed distribution for Linux, conda, activestate
- Handling multiple versions of Python on Linux without using pyenv
- User experience: The documentation and information provided on the downloads page should improve. Selecting an operating system, version and the download should be made easier.
- Python manager that can manage environments, Python version and install packages
- Windows Store build sandboxing limitations cause issues for users.
This causes reproducibility issues and affects how we offer support to users.
- Can the limitations be resolved? If the limitations cannot be resolved,
then change the messaging that it cannot be used for development.
- TO DO: Identify how the Windows Store distribution is supported. Whom to contact?
- Can the limitations be resolved? If the limitations cannot be resolved,
then change the messaging that it cannot be used for development.
- Should Packaging tools support Python shipped without venv? Should packaging tools allow for a situation where Python writes to a file in a temp directory but another process cannot see the file?