github/pyenv
1
0
Fork 0
mirror of https://github.com/pyenv/pyenv.git synced 2024-11-21 20:47:00 -05:00
Code Issues Projects Releases Packages Wiki Activity

Document mirror structure and download cache

Browse source 
in more details
This commit is contained in:
Ivan Pozdeev 2024-06-10 23:20:20 +03:00
parent 7a91070c02
commit 42c66c92d8
1 changed files with 28 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
plugins/python-build/README.md
View file

@ -227,14 +227,30 @@ definition. (All bundled definitions include checksums.)
### Package download mirrors ### Package download mirrors
python-build will first attempt to download package files from a mirror hosted on python-build will first attempt to download package files from a mirror hosted on
GitHub Pages. If a package is not available on the mirror, if the mirror GitHub Pages. If this fails, it will fall back to the
is down, or if the download is corrupt, python-build will fall back to the
official URL specified in the definition file. official URL specified in the definition file.
You can point python-build to another mirror by specifying the You can point python-build to another mirror by specifying the
`PYTHON_BUILD_MIRROR_URL` environment variable--useful if you'd like to run your `PYTHON_BUILD_MIRROR_URL` environment variable.
own local mirror, for example. Package mirror URLs are constructed by joining
this variable with the SHA2 checksum of the package file. Package mirror URLs are constructed by joining
`$PYTHON_BUILD_MIRROR_URL` with the SHA2 checksum of the package file as specified in the URL
in the installation script (the part after the hash sign). E.g.:
```
https://mycache.example.com/0419e9085bf51b7a672009b3f50dbf1859acdf18ba725d0ec19aa5c8503f0ea3
```
If you have replicated the directory structure of an official site, the easiest way to adapt
would be to make symlinks at the mirror's root:
```
0419e9085bf51b7a672009b3f50dbf1859acdf18ba725d0ec19aa5c8503f0ea3 -> 3.10.10/Python-3.10.10.tar.xz
```
The rationale is to abstract away difference between directory structures of sites
of various Python flavors and their occasional changes as well as to accomodate
people who only wish to cache some select downloads. This also allows to mirror multiple sites at once.
If the mirror being used does not have the same checksum (*e.g.* with a If the mirror being used does not have the same checksum (*e.g.* with a
pull-through cache like Artifactory), you can set the pull-through cache like Artifactory), you can set the
@ -247,15 +263,15 @@ mirror by setting the `PYTHON_BUILD_SKIP_MIRROR` environment variable.
The official python-build download mirror is provided by The official python-build download mirror is provided by
[GitHub Pages](http://yyuu.github.io/pythons/). [GitHub Pages](http://yyuu.github.io/pythons/).
### Package download caching ### Package download cache
You can instruct python-build to keep a local cache of downloaded package files Python-build will keep a cache of downloaded package files
by setting the `PYTHON_BUILD_CACHE_PATH` environment variable. When set, package at the location specified by the `PYTHON_BUILD_CACHE_PATH` environment variable
files will be kept in this directory after the first successful download and if it exists. The default is `~/.pyenv/cache`, so you can
reused by subsequent invocations of `python-build` and `pyenv install`. enable caching by just creating that directory.
The `pyenv install` command defaults this path to `~/.pyenv/cache`, so in most The name of the would-be cached file is reported by Pyenv in the "Downloading <filename>..." message.
cases you can enable download caching simply by creating that directory. It's possible to warm up the cache by manually putting the file there under an appropriate name.
### Keeping the build directory after installation ### Keeping the build directory after installation