- Verified all license changes
- Brings us current with the latest releases
- Didn't identify any breaking changes in click
Signed-off-by: Dan Ryan <dan@danryan.co>
The previous help text made it seem that
`pipenv install --dev` would install ONLY
dev-packages, which is not the case.
The current description is identical to the
one used in the documentation, which is
a lot clearer.
By default, `pipenv install` will install packages
based on the list in `Pipfile`, not `Pipfile.lock`.
`pipenv install --dev` is no exception.
I've tested this using pipenv 2018.7.1
with different package versions in `Pipfile`
and `Pipfile.lock`. After `pipenv install`,
the versions in `Pipfile` were the ones
actually installed.
`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.
Signed-off-by: Dan Ryan <dan@danryan.co>
Don't re-clone repos now that this works
Signed-off-by: Dan Ryan <dan@danryan.co>
Prune peeps directory from manifest
Signed-off-by: Dan Ryan <dan@danryan.co>
Fix nonetype uris
Signed-off-by: Dan Ryan <dan@danryan.co>
Manually lock requirements?
Signed-off-by: Dan Ryan <dan@danryan.co>
Update requirementslib - leave context before updating sha
Signed-off-by: Dan Ryan <dan@danryan.co>
Fix requirementslib vcs checkouts
Signed-off-by: Dan Ryan <dan@danryan.co>
fix tmpdir implementation
Signed-off-by: Dan Ryan <dan@danryan.co>
final fix for vcs uris
Signed-off-by: Dan Ryan <dan@danryan.co>
Allow for adding requirements objects directly to pipfile
Signed-off-by: Dan Ryan <dan@danryan.co>
Update piptools patch
Signed-off-by: Dan Ryan <dan@danryan.co>
Dan Ryan
kennethreitz