-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
Official Portable Python Distribution #135011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, this kind of feature needs to be discussed first on https://discuss.python.org/c/ideas/6 and I'm pretty sure that there already exists a topic on having a portable installation. I'm not sure it's possible to do it though as there are many requirements that depend on the host platform and that cannot be carried over. I also don't think the current installer is problematic. For Windows we have a new installer now, and for Unix-based systems, it's pretty much a matter of an |
An installer inherently creates system-wide files and directories, that should be (manually) identified removed when you finish your job. |
In this case, I'd suggest using docker. |
And you can avoid this by building from source and install wherever you want. You can then simply delete this folder. |
This is a feature request for the whole Python user-base; with the goal of making Python significatly better. |
Uh oh!
There was an error while loading. Please reload this page.
Feature or enhancement
Proposal:
An official portable Python distribution would provide a plug-and-play, self-contained interpreter that can be extracted, used, and disposed without the overhead of the traditional installer. Key benefits include:
.zip
extraction), and removal (a simple delete folder operation).This would lower the barrier to entry for many potential users—students and teachers in particular—by promoting no-cost exploration and experimentation.
Implementation:
A practical first step would be to build on the existing embeddable distribution by bundling
pip
and enabling support for environment variables likePYTHONPATH
. This would blend the embeddable build’s isolation with the full-featured usability expected in a portable end-user package.Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
The text was updated successfully, but these errors were encountered: