-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
declare "extras" in requirements.txt #1161
Labels
auto-locked
Outdated issues that have been locked by automation
Comments
+1 |
See issue #1795 |
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. |
== @rbtcollins |
Yea I agree. Going to close this. |
lock
bot
added
the
auto-locked
Outdated issues that have been locked by automation
label
Jun 4, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:/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: