- Exclude python when searching virtualenvs created using nested
virtualenv interpreters (via `lib-dynload` library directory)
Signed-off-by: Dan Ryan <dan@danryan.co>
- Clean up test config and environment variable handling
- Unset env var changes performend by `pipenv run`
- Make `environments.is_in_virtualenv()` more dynamic -- read
environment on the fly
- Split up tests on `pipenv run` to reduce complexity -- one test for
global run (no virtualenv creation), one test for virtualenv creation
- Add `warn_in_virtualenv` call to `run` command, why doesn't click
invoke this automatically?
Signed-off-by: Dan Ryan <dan@danryan.co>
- Fix implementation of `auto_envvar_prefix`
- Pass context setting directly to each command to prevent
`PIPENV_<CMD>_<OPTION>` syntax, implementation will use
`PIPENV_<OPTION>` directly (e.g. `PIPENV_DEV=1` or `PIPENV_SYSTEM=1`
- Fixes#3278
Signed-off-by: Dan Ryan <dan@danryan.co>
- Parsing of markers in non-editable vcs requirements was broken
- This PR adds some VCS repos, some utility pipfile generation functions
and some fixture helpers
- Fixes#3249
Signed-off-by: Dan Ryan <dan@danryan.co>
`if no packages are given` sounds a bit better than
`if none is given` when referring to `provided packages`.
Also mention that `pipenv install` with no provided packages
installs all packages from Pipfile. It is not obvious for
people new to pipenv whether pipenv is using Pipfile or
Pipfile.lock by default.
frostming