Setuptools extension for installing requirements
Project description
Pip Setuptools Extension
========================
|Version| |Downloads| |Status| |License|
A `setuptools`_ extension that installs requirements based on `pip`_
requirements files.
Wait... Why? What??
-------------------
Installing runtime dependencies is already handled by setuptools right?
It's as easy as running ``python setup.py develop``?! Not quite...
*setup.py* is a great tool and the *develop* command is useful for setting
up basic development and installing the dependencies identified by the
``setup_requires`` keyword. What it does not do is install any tools that
are used for actually hacking on the code base. Many projects include a
`pip-formatted requirements file`_ named *requirements.txt* for this very
purposes. It contains the dependencies that you need to have installed to
work on the project instead of use it. This extension aims to automate
that pattern and make it easier to set up a development environment by
providing a new setup command named
:ref:`requirements <requirements-command>`.
Having a separate *requirements.txt* is a good pattern but it is not
without its flaws. Having dependencies identified in two places is an
outright violation of the *Don't Repeat Yourself* principle. That is
something else that we can solve pretty easily with a function that you
can read a pip-formatted requirements file and generate a list that is
usable as the setup ``setup_requires``, ``install_requires``, or
``tests_require`` keywords. This is where the
:func:`~setupext.pip.read_requirements_from_file` function comes in.
You can use this function to populate the ``setup_requires``,
``tests_require``, and ``extras_require`` keywords.
Ok... Where?
------------
+---------------+-------------------------------------------------+
| Source | https://github.com/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
| Status | https://travis-ci.org/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
| Download | https://pypi.python.org/pypi/setupext-pip |
+---------------+-------------------------------------------------+
| Documentation | http://setupext-pip.readthedocs.org/en/latest/ |
+---------------+-------------------------------------------------+
| Issues | https://github.com/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
.. _setuptools: https://pythonhosted.org/setuptools/
.. _pip: https://pip.pypa.io/en/latest/
.. _pip-formatted requirements file:
https://pip.pypa.io/en/latest/reference/pip_install.html
#requirements-file-format
.. |Version| image:: https://badge.fury.io/py/setupext-pip.svg
:target: https://badge.fury.io/
.. |Downloads| image:: https://pypip.in/d/setupext-pip/badge.svg?
:target: https://pypi.python.org/pypi/setupext-pip
.. |Status| image:: https://travis-ci.org/dave-shawley/setupext-pip.svg
:target: https://travis-ci.org/dave-shawley/setupext-pip
.. |License| image:: https://pypip.in/license/setupext-pip/badge.svg?
:target: https://setupext-pip.readthedocs.org/
========================
|Version| |Downloads| |Status| |License|
A `setuptools`_ extension that installs requirements based on `pip`_
requirements files.
Wait... Why? What??
-------------------
Installing runtime dependencies is already handled by setuptools right?
It's as easy as running ``python setup.py develop``?! Not quite...
*setup.py* is a great tool and the *develop* command is useful for setting
up basic development and installing the dependencies identified by the
``setup_requires`` keyword. What it does not do is install any tools that
are used for actually hacking on the code base. Many projects include a
`pip-formatted requirements file`_ named *requirements.txt* for this very
purposes. It contains the dependencies that you need to have installed to
work on the project instead of use it. This extension aims to automate
that pattern and make it easier to set up a development environment by
providing a new setup command named
:ref:`requirements <requirements-command>`.
Having a separate *requirements.txt* is a good pattern but it is not
without its flaws. Having dependencies identified in two places is an
outright violation of the *Don't Repeat Yourself* principle. That is
something else that we can solve pretty easily with a function that you
can read a pip-formatted requirements file and generate a list that is
usable as the setup ``setup_requires``, ``install_requires``, or
``tests_require`` keywords. This is where the
:func:`~setupext.pip.read_requirements_from_file` function comes in.
You can use this function to populate the ``setup_requires``,
``tests_require``, and ``extras_require`` keywords.
Ok... Where?
------------
+---------------+-------------------------------------------------+
| Source | https://github.com/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
| Status | https://travis-ci.org/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
| Download | https://pypi.python.org/pypi/setupext-pip |
+---------------+-------------------------------------------------+
| Documentation | http://setupext-pip.readthedocs.org/en/latest/ |
+---------------+-------------------------------------------------+
| Issues | https://github.com/dave-shawley/setupext-pip |
+---------------+-------------------------------------------------+
.. _setuptools: https://pythonhosted.org/setuptools/
.. _pip: https://pip.pypa.io/en/latest/
.. _pip-formatted requirements file:
https://pip.pypa.io/en/latest/reference/pip_install.html
#requirements-file-format
.. |Version| image:: https://badge.fury.io/py/setupext-pip.svg
:target: https://badge.fury.io/
.. |Downloads| image:: https://pypip.in/d/setupext-pip/badge.svg?
:target: https://pypi.python.org/pypi/setupext-pip
.. |Status| image:: https://travis-ci.org/dave-shawley/setupext-pip.svg
:target: https://travis-ci.org/dave-shawley/setupext-pip
.. |License| image:: https://pypip.in/license/setupext-pip/badge.svg?
:target: https://setupext-pip.readthedocs.org/
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
setupext-pip-1.0.3.tar.gz
(8.2 kB
view hashes)