Skip to content
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

Closed
ewjoachim opened this issue Aug 22, 2013 · 5 comments
Closed

declare "extras" in requirements.txt #1161

ewjoachim opened this issue Aug 22, 2013 · 5 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@ewjoachim
Copy link
Member

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 :

package1==1.2.3
package2==4.5.6

[specific_feature]
package3

[other_feature]
package4

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 just pip install -r requirements.txt to install packages 1 and 2

Thank you

@boblannon
Copy link

+1

@piotr-dobrogost
Copy link

See issue #1795

@rbtcollins
Copy link

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.

@sigmavirus24
Copy link
Member

== @rbtcollins

@dstufft
Copy link
Member

dstufft commented May 12, 2015

Yea I agree. Going to close this.

@dstufft dstufft closed this as completed May 12, 2015
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

6 participants