Add the option to create other sections in Pipfile

A common pattern in Django projects is spliting requirements in differents files. We do this in our company following the recommendations of the Two Scoops of Django of @pydanny and @audreyr. In cookiecutter-django you can see this patterns: https://github.com/pydanny/cookiecutter-django/tree/master/{{cookiecutter.project_slug}}/requirements

So, my thought is that pipenv needs to provide more options besides the regular pipenv install and pipenv install --dev. Maybe something like pipenv install requests --section=production and then pipenv install --section=production to install all the production related packages.

[kennethreitz]

not happening. explicitly designed for just two groups.

[patcon]

Just want to add a use-case of how the two groups are less-than-ideal, although workable:

I would suggest that “groups” are for humans. they are for helping us organize are minds and the projects our minds build. in rubygems land, groups can be arbitrarily named. assuming that prod and dev as the distinction is not something that ecosystem tries to impose.

Example

One project I’m interested in doesn’t even use python on the production website, but has some processing tasks that happen locally to build assets. The two groups it wants to make distinction between are “devserver” (a mock api server that runs in python only locally) and “processing” (a bunch of long-compiling scientific packages for doing geospatial work). Forcing a project like this in the dev/prod dichotomy makes less sense.

Conclusion

Basically, I feel that the distinction is more opinionated than need be, and prevents the tool from speaking human in the way that users might like it to. In my example, we need to have docs (in the CLI instructions and the code comments) to explain this, instead of just having intuitive names of the groups that can go in a command line flag 😃

Anyhow, thanks so so much for all your hard work. Just wanted to provide a counter-point. Everything is work-aroundable, but I simply would contest that it shouldn’t need to be – it seems a reasonable ask. (fwiw, as someone who comes from php land, i feel rubygems and maybe go is the package management ecosystem to emulate, not composer)

Y’all are awesome! ❤️