-
Notifications
You must be signed in to change notification settings - Fork 4
pymanager - proxy support for offline installs #128
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
It's supposed to be using the proxy automatically, we pass the As for the offline install, it looks like you've installed the MSI, which doesn't include an offline package by default. You need the MSIX (or the Store install) for that, or you need to do a |
Okay, I very quickly found a reference (not public, I'm afraid) saying that the flag doesn't do what it says, and we still need to specifically look up the proxy for the URL. I'll add it for the next update, looks pretty straightforward. |
Hello
I prefer to use the msi as that is installed as a system application.
And that was a requirement for me. With the msix seems to use only the user folders
The goal is to provide a python management on system level that allows all users within the development server to be able to management the python environment. This seems plausible using the install options.
The issue is now to manage this in a closed environment.
In terms of the offline installation, I got those logs after doing “py install --download=./ default” . The goal is to have the tool download the required packages and zip files and adapt the json file as a relative file.
I was able to hack a “bundled” folder that is placed in the “C:\Program Files\Pymanager\” and use the fallback-index.json file placed there with relative files path to download and install the required zip packages.
But this is a solution that I believe could be performed with that download options, using the proxy.
Also I would propose actually to bundle within the distribution the python files in the bundled folder also for the msi and include more than the last beta.
There are similar use cases when using tools like UV , and hatch that perform management of python Installations
Regards
Jose
|
The MSIX is installed once for all users, and any user can do the installation. There are ways to deploy to all users automatically (discussed briefly in the documentation, but it's not a scenario we care to support upstream). The MSI will involve you doing a bit more work, but that's why we put it there.
This is intentionally supported, so if it works for you, go ahead. You can also specify some global settings in the HKLM registry if you want to put the fallback files elsewhere - read the docs for this info. These will work even if someone installs the MSIX themselves.
Afraid this isn't going to happen, if only because of the file size. The Python Install Manager is about 10MB, but each Python runtime is about 40MB. Even including the current stable1 is unreasonably misbalanced, but we really want our main installer (the MSIX) to be copyable to an offline machine, installed, and have Python be available. However, you're welcome to create your own MSI from the files that bundles whatever you like. Especially for managing across your own machines. You just don't get it "for free" from our volunteers. Footnotes
|
Background
I have downloaded the latest pymanager and i wanted to perform a offline installation
my windows server can only go to internet via proxy. and even tough we configured "netsh winhttp set proxy :" .
I see it stills tries to get it directly.
Details
logs attached.
python_install_20250606161106_8452.log
The text was updated successfully, but these errors were encountered: