Config to make pipenv install dev dependencies by default
Problem:
In all our repos we have most dependencies that we use locally during development as dev-dependencies. I cannot count how many times people who use our repos (including myself) have been debugging problems that stem from us forgetting the --dev flag when running pipenv sync or pipenv install. This can be quite frustrating (and that frustration is of course our own fault).
Only installing default packages is only done by our CI/CD pipelines.
Proposed solution:
It would be really nice if it was possible to make pipenv install dev-dependencies by default, maybe by setting some environment variable like PIPENV_ALWAYS_INSTALL_DEV_DEPENDENCIES=True or similar which we could then have as part of our developer computer setup.
Rather than support a boolean flag for just dev dependencies, I would be more supportive of a solution that allowed specifying
PIPENV_DEFAULT_CATEGORIES=category1,category2,categoryn
It is more extensible and solves the problem for named categories as well, the idea is if its specified and no --categories override or --dev flag is passed, those lock/upgrade/update/install commands will fallback to the PIPENV_DEFAULT_CATEGORIES
Where do you draw the line for using default categories? Commands like check and uninstall also support a --categories flag, but it wouldn't make sense for them to default to a specific value
I only support the use of the environment variable with the pipenv install and pipenv sync commands, with a more accurate name such as PIPENV_DEFAULT_INSTALL_CATEGORIES