# ripe [](https://travis-ci.org/shaunvxc/ripe) [](https://badge.fury.io/py/ripe) [](http://forthebadge.com) An unnecessary micro-optimization for those who (like me) spend too much time using –force-reinstall or pip uninstall/install while testing every little incremental change to their packages.
## Why? If you find yourself in a workflow where you are continuously reinstalling local copies of your packages to test out changes, you might find ripe to be a useful little hack.
While pip itself offers equivalent functionality with its –force-reinstall flag, ripe will accomplish the same thing in fewer keystrokes.
## Usage
Run from the root-level of a package to uninstall the currently installed version, and reinstall using your local changes:
$ ripe
You can also point ripe to the package you wish to reinstall with your local changes:
$ ripe packagename
For more complicated paths:
$ ripe /path/to/local/package
In all cases, ripe will automatically pass y to the Proceed (y/n) prompt for uninstalling.
*Note* ripe must either be run from or pointed to a pip-installable location (it checks for setup.py. If it is run from elsewhere, it will tell you as much before exiting)
## Installation
$ pip install ripe
#### Disclaimer This is a little tool that uses os.system() to pip uninstall and pip install the local copy of your package onto your system (or current virtual environment). As such this package should only be used locally and properly.
Metadata
Release files for ripe 0.0.4
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 |
|---|---|---|---|---|
| ripe-0.0.4.tar.gz | 4.0 kB | Without provenance | Details for ripe-0.0.4.tar.gz |
Release files / ripe-0.0.4.tar.gz
| Download URL | ripe-0.0.4.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34834b1cde52a1ae5da6f18b907c299bf9add1182cf8001c99b2bc43099f0299
|
|
BLAKE2b-256 checksum How to use checksums |
02d777fb31559f76aabd7813727dbd8238b51404a352223e5545acd54c3ccbff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ripe 0.0.4
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.