- Fix dependecy resolution for _all_ dependencies which are just
direct URLs or files
- Bypass pip-tools for non-editable requirements which can be resolved
- Fixes#3148
Signed-off-by: Dan Ryan <dan@danryan.co>
Carets introduce a difficult situation since they are essentially
"lossy" when parses. Consider this in cmd.exe:
> echo "foo^bar"
"foo^bar"
> echo foo^^bar
foo^bar
The two commands produce different results, but are both parsed by the
shell as `foo^bar`, and there's essentially no sensible way to tell what
was actually passed in. This implementation assumes the quoted variation
(the first) since it is easier to implement, and arguably the more common
case.
- Fix `PIPENV_PYTHON` envvar which auto-recreated environments due to
`auto_envvar_prefix`, now it is not pulled from the environment
automatically
- Fix formatting of some news entries
- Automate release via `inv release.release` (will be aliased)
Signed-off-by: Dan Ryan <dan@danryan.co>
- Stop preferring resolution of VCS dependencies in all cases
- Resolve vcs dependencies together with non-vcs dependencies
- Clarify blocking and no-deps logic
- Add artifacts and tests
- Add vendoring task for artifacts
- Clean up release tasks
- Fixes#3296
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>