Prepare for '2.1.0' release
This commit is contained in:
parent
02e0379951
commit
e4dd1118c1
14
CHANGES.md
14
CHANGES.md
|
@ -1,8 +1,18 @@
|
|||
Changelog
|
||||
=========
|
||||
|
||||
2.0.0 (stable)
|
||||
--------------
|
||||
2.1.0
|
||||
-----
|
||||
|
||||
* JSON output is sorted alphabetically to make it deterministic
|
||||
|
||||
* Fix --freeze option due to breaking changes in pip's internal api in
|
||||
version > 21.1.1
|
||||
|
||||
* Include license file in dist package
|
||||
|
||||
2.0.0
|
||||
-----
|
||||
|
||||
* Support for running in the context of a virtualenv (without
|
||||
installing pipdeptree inside the virtualenv)
|
||||
|
|
|
@ -27,9 +27,8 @@ Installation
|
|||
|
||||
$ pip install pipdeptree
|
||||
|
||||
pipdeptree has been tested with Python versions ``2.7``, ``3.4``,
|
||||
``3.5``, ``3.6``, ``3.7``, ``3.8``, ``3.9-dev`` as well as ``pypy2``
|
||||
and ``pypy3``.
|
||||
pipdeptree has been tested with Python versions ``2.7``, ``3.5``,
|
||||
``3.6``, ``3.7``, ``3.8``, ``3.9`` as well as ``pypy2`` and ``pypy3``.
|
||||
|
||||
Python ``2.6`` is way past it's end of life but if you ever find
|
||||
yourself stuck on a legacy environment, version ``0.9.0`` *might*
|
||||
|
|
|
@ -31,7 +31,7 @@ from pip._vendor import pkg_resources
|
|||
# from graphviz import backend, Digraph
|
||||
|
||||
|
||||
__version__ = '2.0.0'
|
||||
__version__ = '2.1.0'
|
||||
|
||||
|
||||
flatten = chain.from_iterable
|
||||
|
|
2
setup.py
2
setup.py
|
@ -44,10 +44,10 @@ setup(
|
|||
'Programming Language :: Python',
|
||||
'Programming Language :: Python :: 2.7',
|
||||
'Programming Language :: Python :: 3',
|
||||
'Programming Language :: Python :: 3.4',
|
||||
'Programming Language :: Python :: 3.5',
|
||||
'Programming Language :: Python :: 3.6',
|
||||
'Programming Language :: Python :: 3.7',
|
||||
'Programming Language :: Python :: 3.8',
|
||||
'Programming Language :: Python :: 3.9'
|
||||
]
|
||||
)
|
||||
|
|
Loading…
Reference in New Issue