New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pipenv update --outdated generates no output #2828

Closed
yunti opened this Issue Sep 6, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@yunti

yunti commented Sep 6, 2018

Issue description

pipenv update --outdated
generates no output.

Expected result

Something like 'all packages are upto date"

Actual result

It looks like it's working to check if anything is outdated and presumably finds nothing is outdated. However nothing is printed to the screen so no way to tell what has happened.

Steps to replicate

Provide the steps to replicate (which usually at least includes the commands and the Pipfile).


Please run $ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.

If you're on macOS, run the following:

$ pipenv --support | pbcopy

If you're on Windows, run the following:

> pipenv --support | clip

If you're on Linux, run the following:

$ pipenv --support | xclip

techalchemy added a commit that referenced this issue Oct 30, 2018

Fix virtualenv path derivations
- Fix inadvertent occasional global installation of files
- Fix inadvertent occcasional global removal of files
- Fix empty output from `pipenv update --outdated`
- Fixes #2828
- Fixes #3113
- Fixes #3047
- Fixes #3055

Signed-off-by: Dan Ryan <dan@danryan.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment