Ever did a mistake to ``pip install`` in the terminal when installing
packages from ``requirements.txt`` file like following?
::
$ pip install requirements.txt
Collecting requirements.txt
Could not find a version that satisfies the requirement requirements.txt (from versions: )
No matching distribution found for requirements.txt
Now you wont. Thanks to some nasty hacks and tricks there is a package
on PyPI that handles that. It finds the desired requirements file and
installs it in your current environment.
::
echo "gevent" > requirements-dev.txt
pip install requirements-dev.txt
This package was made only for trolling so do not expect it to work. It
may work on Linux and Mac OS X but was not extensively tested. It is
also a one-shot trick so no updates will be installed once you do that
unless you specify a ``-U`` or ``--update`` switch. Happy debugging!
PyPI (fortunately) does not allow to upload package named
``requirements.txt`` so the only supported name is currently a
``requirements-dev.txt``. It still should be quite popular though.
.. |PyPI| image:: https://img.shields.io/badge/downloads-enough-ff69b4.svg
:target:
1 maintainer
Metadata
1 maintainer
Release files for requirements-pyconpl2016.txt 0.0.0
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 | |
|---|---|---|---|---|
| requirements-pyconpl2016.txt-0.0.0.tar.gz | 3.1 kB | Without provenance | Details |
Release files / requirements-pyconpl2016.txt-0.0.0.tar.gz
| Download URL | requirements-pyconpl2016.txt-0.0.0.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52ca712ae4661419d4afd83c01295469270781473a57e60e5d4f46494a438995
|
|
BLAKE2b-256 checksum How to use checksums |
2fd5dee660db13fd390e35f6e90a81c604a0093b417ad021606664a6af943ced
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for requirements-pyconpl2016.txt 0.0.0
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.
