You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like the flexibility pip-compile provides for inputting a requirements.in and outputting a requirements.txt that also pins dependencies.
Unfortunately, my company doesn't use requirements.txt, we solely center on setuptools.setup's install_requires=["pgk==1.0.0", ...] for our internal packages. So direct use of pip-compile will not out-of-the-box work for us.
One possible workaround is to use requirements.in with pip-compile and have setuptools.setup read from the generated requirements.txt as described here (simple) or here (advanced).
However, this is a workaround and requires:
Deviation from our setup.py-only workflow
DIY parsing of a requirements.txt
Describe the solution you'd like
I would like to see pip-compile somehow directly integrate with setuptools.setup's install_requires.
The main benefit is enabling a new workflow: stay close to a package's setup.py (and not adding an extra indirection: the inclusion + parsing of a requirements.txt file).
One possible solution is enabling pip-compile to be input a requirements.in with a flag (e.g. --to-setup path/to/setup.py) that, instead of creating a requirements.txt will update the install_requires inside of a setup.py (or alternately a pyproject.toml, for future users).
Alternative Solutions
I have read a bunch of issues here, and I believe this request hasn't been made before.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
What's the problem this feature will solve?
I really like the flexibility
pip-compile
provides for inputting arequirements.in
and outputting arequirements.txt
that also pins dependencies.Unfortunately, my company doesn't use
requirements.txt
, we solely center onsetuptools.setup
'sinstall_requires=["pgk==1.0.0", ...]
for our internal packages. So direct use ofpip-compile
will not out-of-the-box work for us.One possible workaround is to use
requirements.in
withpip-compile
and havesetuptools.setup
read from the generatedrequirements.txt
as described here (simple) or here (advanced).However, this is a workaround and requires:
setup.py
-only workflowrequirements.txt
Describe the solution you'd like
I would like to see
pip-compile
somehow directly integrate withsetuptools.setup
'sinstall_requires
.The main benefit is enabling a new workflow: stay close to a package's
setup.py
(and not adding an extra indirection: the inclusion + parsing of arequirements.txt
file).One possible solution is enabling
pip-compile
to be input arequirements.in
with a flag (e.g.--to-setup path/to/setup.py
) that, instead of creating arequirements.txt
will update theinstall_requires
inside of asetup.py
(or alternately apyproject.toml
, for future users).Alternative Solutions
I have read a bunch of issues here, and I believe this request hasn't been made before.
Additional context
n/a
The text was updated successfully, but these errors were encountered: