Skip to content
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

Consider adding "pipenv outdated" as an alias for "pipenv update --outdated" #2624

Closed
K900 opened this issue Jul 22, 2018 · 5 comments
Closed
Labels
Status: Requires Approval This issue requires additional approval to move forward. Type: API Change This issue describes an API change. Type: Behavior Change This issue describes a behavior change. Type: Discussion This issue is open for discussion.

Comments

@K900
Copy link
Contributor

K900 commented Jul 22, 2018

Pipenv doesn't support outdated as a separate subcommand, making the functionality sort of hard to reach. Yarn, npm, Composer, RubyGems, Bundler and Cargo (via a third party plugin) all support $package_manager outdated directly. It would be nice for Pipenv to be consistent here, as many people working on full stack projects probably have muscle memory for it (I know I do :) ).

@techalchemy
Copy link
Member

This is a good suggestion and a good reason. I'll triage it with Kenneth and see what he thinks

@techalchemy techalchemy added Type: Discussion This issue is open for discussion. Type: Behavior Change This issue describes a behavior change. Type: API Change This issue describes an API change. Status: Requires Approval This issue requires additional approval to move forward. labels Jul 24, 2018
@uranusjr
Copy link
Member

Probably worth considering whether we should keep update --outdated, or remove it in favour of outdated (maybe through a deprecation cycle).

@charlax
Copy link
Contributor

charlax commented Jul 17, 2019

What would be nice too would be to take inspiration from yarn's outdated command, which uses a color code (for semver updates) and includes as link to the project (super useful to check the changelog):

% yarn outdated
yarn outdated v1.17.3
info Color legend :
 "<red>"    : Major Update backward-incompatible updates
 "<yellow>" : Minor Update backward-compatible features
 "<green>"  : Patch Update backward-compatible bug fixes
Package                Current Wanted Latest Package Type    URL
@babel/core            7.5.0   7.5.4  7.5.4  devDependencies https://babeljs.io/

@matteius
Copy link
Member

matteius commented Jan 9, 2022

Noting here that this issue is rather old at this point, but also there is a recent issue with an open PR that seems to be fulfilling a very similar ask to this by adding an out dated check. #4893

Perhaps we should close this issue and rally behind the open PR?

@matteius
Copy link
Member

#4893 had been merged in and next release of pipenv (or running the master branch) gives you the pipenv verify command. I am closing this issue out as I believe that command covers this use case. The command doesn't currently doesn't output which things are outdated but that could be a potential future enhancement. Right now you get:

$ pipenv verify
Pipfile.lock is up-to-date.

or

$ pipenv verify
Pipfile.lock is out-of-date. Run $ pipenv lock to update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Requires Approval This issue requires additional approval to move forward. Type: API Change This issue describes an API change. Type: Behavior Change This issue describes a behavior change. Type: Discussion This issue is open for discussion.
Projects
None yet
Development

No branches or pull requests

5 participants