- Notifications
You must be signed in to change notification settings - Fork11
Description
Background
Currently, for offline installation of a Python version usingpymanager
, the recommended workflow is as follows:
- Use the
--download
option to download the ZIP package into a directory. - Generate an
index.json
file in that directory. - When installing, use the
--source
option to specify the correspondingindex.json
.
While this method works, it introduces unnecessary steps, especially since the ZIP package or directory often contains all the information needed for installation.
Proposed Improvement
Why can't we install a Python version directly from a ZIP package or directory, without requiring anindex.json
?
For modern Python packages generated fromPC/layout
(with the--include-install-json
parameter enabled) they already have__install__.json
, and the resulting ZIP or directory already includes everything necessary for installation. In these cases,pymanager
should be able to install directly from the package or directory.
Use Case
For example, when I compiled a CPython version by myself and packaged it usingPC/layout
, the output result would either be a directory or a ZIP file package. To install usingpymanager
, I had to manually create anindex.json
file, which was neither convenient nor beneficial for users.
Another typical scenario is when I use the--download
command to fetch a Python package ZIP file on a device with internet access, and then copy that ZIP file to a target device that cannot connect to the internet.
On the target device, the local directory only contains this specific ZIP file package. Even if there are multiple packages, they are all stored in a unified naming format ofpythoncore-3.xx-(32|64)-3.xx.xx
. In this case, the user does not care about the different Python versions in the directory, and does not need to useindex.json
for indexing or matching version tag from command-line parameters. The intention is clear:I only want to install the contents of this ZIP file package
Requiring the use ofindex.json
in such a case introduces unnecessary complexity and steps for a straightforward, single-package installation. Supporting direct installation from the ZIP package would greatly improve the user experience, especially for offline and isolated environments.
Suggestion
Please consider supporting direct installation from a ZIP package or directory, especially when it already contains all required installation files (including__install__.json
). This will simplify the workflow for offline installations and make it easier for users compiling their own Python builds.