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 ofpip
was available from thePATH
, 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 callpython -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 installpip-review
, has been modernized. Features fromsetuptools
are used to indicate supported Python versions and conditional dependencies. It appears that this may sometimes preventpip
from installingpip-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.