https://github.com/shir0kamii/pipin

Pin your requirements versions
https://github.com/shir0kamii/pipin

pip requirements versioning

Last synced: 10 days ago
JSON representation

Pin your requirements versions

• Host: GitHub
• URL: https://github.com/shir0kamii/pipin
• Owner: Shir0kamii
• Created: 2018-01-16T22:40:48.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-08-16T16:41:33.000Z (over 6 years ago)
• Last Synced: 2024-11-29T04:39:42.041Z (26 days ago)
• Topics: pip, requirements, versioning
• Language: Python
• Size: 1.95 KB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.rst

Awesome Lists containing this project

README

        
Pipin

=====

.. image:: https://media.giphy.com/media/l2Sqir5ZxfoS27EvS/giphy.gif

Pin packages in your requirements files with versions from your environment.

Status

------

Pipin is maintained, feel free to open issues or pull requests.

I want to get it!

-----------------

Okay, then please use pip to do so::

    pip install pipin-req

Yeah, pipin was already taken, so sad. :(

How do I use it?

----------------

Pipin is meant to be used from the command line. Just pass it the requirement

file in which you want to pin versions::

    pipin requirements.txt

It also works with multiple filenames::

    pipin requirements/docs.txt requirements/tests.txt

For each package it encounters that doesn't have a pinned version, pipin will

search in your python environment for that package. If it find a matching

package, its version will be used.

Why should I use it?

--------------------

My use case was templating. When I create a project, I have a bunch of

unpinned dependencies (as I want to begin a project with latest versions).

I made this project to pin their versions once my virtualenv is setup.

Why the name pipin?

-------------------

It's the contraction of *pip* and *pin*. A simple word play!