Flask-Pypi-Proxy
A pypi proxy done using flask. It will use PyPI, and then keep the downloaded egg for future reference. After the package is downloaded from PyPI, it won’t download it from PyPI again and instead use the local copy of the file.
How to use it
To use it after the right configuration, run:
pip install -i http://mypypiserver.com/simple/ <PACKAGE>
Documentation can be found here: https://flask-pypi-proxy.readthedocs.org/en/latest/index.html
Advantages
A local PyPI mirror to download the eggs faster and doesn’t depends on Pypi or any other service.
Uploading your private python packages. This is useful if you work for a company that have eggs, but doesn’t open source them :(
Uploading the compiled packages. There are some packages (lxml, Pillow) that are compiled each time that are installed. You can upload the compiled package to save some time.
It does get newer versions. Supose that you installed Flask (0.8.0), and a new release is required. This is version 0.9. Then the new package will be downloaded from PyPI, and the proxy will be updated
Special Thanks
Special thanks to robin-jarry and to jokull
Metadata
Release files for Flask-Pypi-Proxy 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Flask-Pypi-Proxy-0.5.1.tar.gz | 8.5 kB | Without provenance | Details for Flask-Pypi-Proxy-0.5.1.tar.gz |
Release files / Flask-Pypi-Proxy-0.5.1.tar.gz
| Download URL | Flask-Pypi-Proxy-0.5.1.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
537f84e392853ce4fbfc57c96eaa88e43f70355553d56f419390ad7ce14040ba
|
|
BLAKE2b-256 checksum How to use checksums |
0b55141710e510ac16d9188147fbad0c3f553b99ebfb044bfe3d334a60838eb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Flask-Pypi-Proxy 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.