Copyright (c) 2015 Sebastian Vetter
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
.. image:: https://travis-ci.org/elbaschid/pipev.svg?branch=master
*pipev* is a wrapper around [`pip`](https://pip.pypa.io), the Python package
manager maintained by the PyPA.
*pip* is a great tool to manage dependencies and install applications. I really
❤ it! It currently lacks a tiny little feature though: expanding environment
variables in *requirement files*.
A use case that I've come across several times is using the VCS support in
a `requirement.txt` file with a private github repository. Using an OAuth token
to grant access to the private repository means storing that token in the
`requirments.txt`...which is 🙈. It would look something like this::
Wouldn't it be nice if you could simple do something like this::
*pipev* makes that possible by patching *pip* to expand environment variables
occuring in *requirement* files.
$ pip install pipev
or if you prefer to install from the github repo directly::
$ pip install https://github.com/elbaschid/pipev/archive/master.zip
Just use `pipev` instead of `pip` for your install command. You can basically
use `pipev` everywhere instead of `pip` but it will only effect calls related
to loading *requirements files*::
$ pipev install -r requirements.txt
Install all the requirements for development::
$ pip install -e ".[dev]"
Run the tests::
Run these commands::
$ bumpversion (major|minor|patch)
$ make release
This code is licensed under the `MIT License`_.
.. _`MIT License`: https://github.com/elbaschid/pipev/blob/master/LICENSE
Classifier: Development Status :: 1 - Planning
Classifier: License :: OSI Approved :: MIT License
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: Implementation :: CPython
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.