Run pip outside of environment
At a glance:
$ virtualenv --no-pip myenv # Create environment without pip.
$ source myenv/bin/activate # Activate environment.
$ pip --version # pip is not available.
bash: pip: command not found
$ ouo install six # But we can still do this.
Collecting six
Using cached six-1.15.0-py2.py3-none-any.whl (10 kB)
Installing collected packages: six
Successfully installed six-1.15.0
$ python -c 'import six; print(six.__file__)'
.../myenv/lib/python3.9/site-packages/six.py
How?
ouo downloads pip wheels into the user's data dirctory. When executed, it
executes pip with something like
/path/to/python /path/to/pip-20.3.3-py2.py3-none-any.whl/pip
where the path of the Python interpreter is detected with the VIRTUAL_ENV
environment variable. The interpreter would then perform a zip import to
execute the pip module inside the wheel.
Future Works
setuptoolsandwheelare still needed to build legacy (non-PEP-517) source distributions. This makespython -m venv --no-pipunrealistic.- Invocation is slow. This has two causes:
ouoneeds to iterate through the wheel directory to find a suitable pip version for the current Python version. Also, zip imports are very slow.
Metadata
Release files for ouo 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ouo-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / ouo-0.0.2-py3-none-any.whl
| Download URL | ouo-0.0.2-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8fd03b8aaa9fd7d7094be491cea4c72e86fa893400c615f2cfce499b29959fcb
|
|
BLAKE2b-256 checksum How to use checksums |
ee2bd679340e0b0372b0ec4c3e09286ce853c156e976e68f00493d031fc4f5c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.0
|
Security for ouo 0.0.2
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.