1.3.0

What's Changed

• Implement --freeze-outdated-packages argument by @hueseyincelik in #98

New Contributors

• @hueseyincelik made their first contribution in #98

Full Changelog: 1.2.0...1.3.0

1.2.0

What's Changed

• feat: implement --continue-on-fail argument by @5j9 in #92

New Contributors

• @5j9 made their first contribution in #92

Full Changelog: 1.1.1...1.2.0

1.1.1

What's Changed

• remove unused lib by @even-even in #81
• Minor refactor setup py by @even-even in #82
• Fixing constraints bug and modifying README by @Asiier in #86

New Contributors

• @even-even made their first contribution in #81
• @Asiier made their first contribution in #86

Full Changelog: 1.1.0...1.1.1

Some bugfixes and new features and looking for a new maintainer

• Looking for a new maintainer. #76
• Fixed a bug that prevented the README from being visible on the PyPI website. #65
• Fixed the forwarding of unknown arguments to pip. In version 1.0, such arguments would be forwarded to pip list but not to pip install, causing inconsistent behaviour when using, for example, the --user flag. Such usage should now work better. #62
• Added a convenience feature to interactive mode: you can repeat your last answer (y or n) by simply pressing the return key. #70
• Specified the license terms (BSD). #56
• Other minor logic, distribution and documentation fixes. #57, #74, #54, #59, #66

Thanks to @kshitij10496, @cherichy and @joshbode for contributing pull requests to this release.

1.0: Wrapping pip list --outdated

Pip-review dropped its own update-checking logic and now relies on pip list --outdated instead. This improves the consistency with pip and solves many old issues.

• breaking Support for Python 2.6 and Python 3.2 has been dropped entirely. Only Python versions 2.7 and 3.3+ are now supported.
• breaking pip-review is now guaranteed to list the same updates as pip list --outdated. While the reliance on pip list makes pip-review more reliable overall, it does introduce some subtle changes in behaviour. pip-review may find updates that it couldn't detect before. pip-review will also copy errors in the available updates from pip list if those occur. For example, version 7.0 of pip used to include prerelease updates even if the --pre flag wasn't passed. If you are using pip-review in an automated workflow which relies on very particular update detection, you may wish to compare the new behaviour of pip-review with version 0.5.3. #18 #21 #32 #41 #52 #53 #55
• breaking pip-review does not accept the --editables option anymore. Instead, it forwards the --editable option to pip list. Note the disappearance of the trailing 's' in the option name. #32 #53
• Unrecognized options are forwarded unchanged to pip list. As a consequence, you now have much more control over the way in which packages are checked for updates. #6 #21 #27 #32 #53
• The Travis CI build status now accurately reflects the development status in Python versions 2.7, 3.3 and 3.6. #15 #42 #48 #51
• pip-review still support all versions of pip from 1.5.6 onwards. In pip version 9.0 and later, pip list --outdated is called with the additional flag --format=json for maximal reliability. In older versions of pip, a simple but reliable custom parser is used to extract the required information from the text-based output. #32 #41 #53
• Internal calls to pip now universally process the command as a list rather than as a concatenated string. This makes the subprocess behaviour more reliable. #32 #44 #45 #50 #53 #55
• pip-review can now again update itself even if invoked as pip-review. In version 0.5 through 0.5.3, this was only possible if invoked as python -m pip_review. #44 #45 #47

Thanks to @xoviat and @bil-elmoussaoui for making important contributions to this release.

0.5.3

This release contains a bugfix as well as several changes that are part of working towards our 1.0 release.

• breaking pip-review used to call whichever version of pip was available from the PATH, which sometimes caused it to manage package updates for the wrong version of Python. This behaviour is now changed, for the better, under Python version 2.7 and later: pip-review will call python -m pip instead. So from now on, package updates are always specific to the currently used Python environment. #44 #45 #46
• breaking The setup script, which is used by pip to install pip-review, has been modernized. Features from setuptools are used to indicate supported Python versions and conditional dependencies. It appears that this may sometimes prevent pip from installing pip-review. Please report if you run into any issues. #48
• deprecation Support for Python 2.6 and Python 3.2 is now deprecated and will be removed in version 1.0. #45
• The README was converted to reStructuredText. One of the consequences is that it is now automatically shown on the PyPI page. #38
• The documentation now explains that you need to invoke pip-review as python -m pip_review if you wish for pip-review to update itself. This has been both possible and necessary since version 0.5. #47
• The description that is shown when you call pip-review -h has been updated to reflect that pip-review has little to do with dependencies or pinning, compared to the current pip-tools package.

0.5.2

Restores the green build status, thanks to @Flimm (#37).

0.5.1: Bugfix and preparation release.

Bugfix and preparation release.

• breaking pip-review used to contain a bug that caused it to report available updates when the installed version was newer than the latest available from PyPI. This is not the case anymore; it only reports available updates when a newer version is available. (#10 #29 #30 #31)
• Packages like pip, setuptools and wheel are not ignored by pip-review anymore. (#9 #13 #16)
• Broken output formatting in Windows has been fixed. (#14 #16 #17)
• pip-review now explicitly depends on pip. (#16)
• Some changes were made to the test suite to make it more future-proof. (#15 #34 #35 #36)
• The CONTRIBUTING.md was updated.
• The HISTORY.md was deprecated in favor of tag messages and GitHub release notes. It will be removed in a future release. Its final version will remain available here.

Credits: @xoviat @bil-elmoussaoui @Flimm

0.5

pip-review now employs entry points. As a consequence, the pip-review command now works under Windows and can alternatively be called as python -m pip_review. See the HISTORY for further details.

This release was published on PyPI on 2016-10-10, but I forgot to mention it here on GitHub until now (2017-01-20).

Issues closed and pull requests merged in this release: #2 #3 #4 #11 #12. Credits: @rvause @Gillingham.

0.4

From now on, pip-review ignores pre-release versions by default. To include pre-release versions, as in version 0.3.7 and before, pass the --pre flag. Thanks to @rvause for pull request #1.