[<img src="https://img.shields.io/pypi/v/pip-save.svg">](https://pypi.python.org/pypi/pip-save)
pip-save is a simple wrapper around **pip** so as to add ```npm --save``` style functionality to pip.
Currently its a big pain while installing new dependencies using pip. After installing the dependency,
you need to figure out the version number and then manually add it to your requirements file.
``pip-save`` allows you to install/uninstall any dependecy and automatically add/remove
it to/from your requirements file using one command only.
Since its only a wrapper around pip install and uninstall commands,
it accepts all options/config as these commands.
#### Installation
$ pip install pip-save
####Use
To Install a package and add it to your requirements.tx
$ pip-save install [<list of packages>]
To upgrade a package
$ pip-save install --upgrade [<list of packages>]
To uninstall a package and remove it from your requirements.txt
$ pip-save uninstall [<list of packages>]
To install a package from VCS and add it to your requirements file
$ pip-save install -e <url of the repo>
#### Configuration
For most users the default configuration of pip-save should be fine. If you do
want to change pip-save's defaults you do so by adding configuration options to
a configuration file. If a `.pipconfig` file exists in the current working
directory, its automatically loaded.
Here is an example of available options along with their default values.
[pip-save]
requirements = requirements.txt
use_compatible = False
##### Configuration Options
* requirements:- path to the requirements file to be used. Default value is `requirements.txt`
Can be overwritten by using command line option `-r` or `--requirement`
* use_compatible:- whether to use compatible version specifier instead of exact versions.
Default value is `False`. Can be overwritten by using command line flag `--use-compatible`
Metadata
Release files for pip-save 0.2.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 | Actions |
|---|---|---|---|---|
| pip-save-0.2.0.tar.gz | 5.9 kB | Without provenance | Details for pip-save-0.2.0.tar.gz |
Release files / pip-save-0.2.0.tar.gz
| Download URL | pip-save-0.2.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b1fb5154d5aa7e7c6b6fc9695c0265579cfb8e608c2ddae5d6e32ce3965ce37
|
|
BLAKE2b-256 checksum How to use checksums |
2032b2a0e07c2419bd1c9fccc7582c94dea9df49bbe183d1c3f98c19216709ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pip-save 0.2.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.