ChangelogΒΆ
Next feature release
[Support]: Remove some apparently non-functional
setup.py
logic around conditionally requiringenum34
; it was never getting selected and thus breaking a couple modules that relied on it.enum34
is now a hard requirement like the other semi-optional-but-not-really requirements.
1.2.2 2018-06-26
- [Bug]:
checks.blacken
had a typo regarding its folder selection argument; the CLI/function arg wasfolder
while the configuration value wasfolders
(plural). It’s been made consistent: the CLI/function argument is nowfolders
. - [Bug]: Was missing a ‘hide output’ flag on a subprocess shell call, the
result of which was mystery git branch names appearing in the output of
inv release
and friends. Fixed now.
1.1.1 2018-06-26
[Bug]:
checks.blacken
had a typo regarding its folder selection argument; the CLI/function arg wasfolder
while the configuration value wasfolders
(plural). It’s been made consistent: the CLI/function argument is nowfolders
.[Bug]: Was missing a ‘hide output’ flag on a subprocess shell call, the result of which was mystery git branch names appearing in the output of
inv release
and friends. Fixed now.[Support]: Remove some apparently non-functional
setup.py
logic around conditionally requiringenum34
; it was never getting selected and thus breaking a couple modules that relied on it.enum34
is now a hard requirement like the other semi-optional-but-not-really requirements.
1.0.1 2018-06-26
[Bug]:
checks.blacken
had a typo regarding its folder selection argument; the CLI/function arg wasfolder
while the configuration value wasfolders
(plural). It’s been made consistent: the CLI/function argument is nowfolders
.[Bug]: Was missing a ‘hide output’ flag on a subprocess shell call, the result of which was mystery git branch names appearing in the output of
inv release
and friends. Fixed now.[Support]: Remove some apparently non-functional
setup.py
logic around conditionally requiringenum34
; it was never getting selected and thus breaking a couple modules that relied on it.enum34
is now a hard requirement like the other semi-optional-but-not-really requirements.
1.2.1 2018-06-18
[Support]: Remove some apparently non-functional
setup.py
logic around conditionally requiringenum34
; it was never getting selected and thus breaking a couple modules that relied on it.enum34
is now a hard requirement like the other semi-optional-but-not-really requirements.
1.2.0 2018-05-22
[Feature]: Add the
checks
module, containingchecks.blacken
which executes the black code formatter. Thanks to Chris Rose.[Feature]: Add ‘missing’ arguments to
pytest.integration
so its signature now largely matchespytest.test
, which it wraps.[Feature]: Break out a generic form of the
travis.sudo-coverage
task intotravis.sudo-run
which can be used for arbitrary commands run under the ssh/sudo capable user generated bytravis.make-sudouser
/travis.make-sshable
.[Feature]: Add
travis.blacken
which wraps the newchecks.blacken
(in diff+check mode, for test output useful for users who cannot themselves simply run black) in addition to performing Travis-oriented Python version checks and pip installation.This is necessary to remove boilerplate around the fact that
black
is not even visible to Python versions less than 3.6.
1.1.0 2018-05-14
- [Feature]: Split out the body of the (sadly incomplete)
packaging.release.all
task into the better-namedpackaging.release.prepare
. (all
continues to behave as it did, it just now callsprepare
explicitly.)
1.0.0 2018-05-08
- [Feature]: Pre-history / code primarily for internal consumption