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
When pkg_resources creates an egg file, the egg_info contains a "requires.txt" that ressembles a lot to the requirements.txt format except that it also contains the "extras" information that the setup.py declares, with brackets tags, having this form :
One would then call it using pip install -r requirements.txt[specific_feature] (to install packages 1, 2 and 3) or just pip install -r requirements.txt to install packages 1 and 2
Thank you
The text was updated successfully, but these errors were encountered:
This doesn't make sense to me. extras are exported metadata about a package. requirements.txt are local pins to facilitate deployments. Any extras needed should be in your setup.cfg / setup.py extra_requires section.
This is a feature request.
When pkg_resources creates an egg file, the egg_info contains a "requires.txt" that ressembles a lot to the requirements.txt format except that it also contains the "extras" information that the setup.py declares, with brackets tags, having this form :
If pip would parse this format, or a format like this, that could reduce a lot the need for having multiple files with a
base.txt
file and all other files beggining with-r base.txt
(see for exemple this folder : https://github.com/twoscoops/django-twoscoops-project/tree/develop/requirements )One would then call it using
pip install -r requirements.txt[specific_feature]
(to install packages 1, 2 and 3) or justpip install -r requirements.txt
to install packages 1 and 2Thank you
The text was updated successfully, but these errors were encountered: