Metadata-Version: 2.1
Name: setup-requirements
Version: 1.0
Summary: Add requirements.txt automatically to wheel dependencies
Home-page: https://github.com/mbachry/setup-requirements
Author: Marcin Bachry
Author-email: hegel666@gmail.com
License: MIT
Platform: unix
Platform: linux
Platform: osx
Platform: cygwin
Platform: win32
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Cython
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: Implementation :: CPython
Requires-Python: >=3.9
Description-Content-Type: text/x-rst
Requires-Dist: wheel

setup-requirements
==================

.. image:: https://github.com/mbachry/setup-requirements/actions/workflows/ci.yaml/badge.svg?branch=master
    :alt: Build status
    :target: https://github.com/mbachry/setup-requirements/actions

A PEP 517 build backend that automatically adds ``requirements.txt``
contents to wheel dependencies.

Usage
-----

Use ``setup_requirements`` as your build backend in ``pyproject.toml``::

  [build-system]
  requires = ['setuptools>=42', 'wheel', 'setuptools_scm[toml]>=3.4']
  build-backend = "setup_requirements"

Notes
-----

This backend should be used if you want to build an **application**
with pinned dependencies. For libraries use standard
``install_requires`` without pins.

The backend exists only because it's not possible to use ``file:`` in
``setup_requires`` (yet?). See this `github issue`_.

.. _github issue: https://github.com/pypa/setuptools/issues/1951

Limitations
-----------

It's not possible to use a different path than a top-level
``requirements.txt`` file.


