Changelog for python3-invoke-1.4.1-4.fc33.noarch.rpm :

* Thu Jul 30 2020 Paul Howarth - 1.4.1-4- Use new-style dependencies, fixes FTBFS due to conflicting pytest requirements
* Wed Jul 29 2020 Fedora Release Engineering - 1.4.1-3- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Sun May 24 2020 Miro Hrončok - 1.4.1-2- Rebuilt for Python 3.9
* Thu Jan 30 2020 Paul Howarth - 1.4.1-1- Update to 1.4.1 (#1796269) - Explicitly strip out \'__pycache__\' (and for good measure, \'.py[co]\', which previously we only stripped from the \'tests/\' folder) in our \'MANIFEST.in\', since at least some earlier releases erroneously included such (GH#586) - Fix an issue with \'~invoke.run\' and friends having intermittent problems at exit time (symptom was typically about the exit code value being \'None\' instead of an integer; often with an exception trace) (GH#660) - Close pseudoterminals opened by the \'~invoke.runners.Local\' class during \'run(..., pty=True)\'; previously, these were only closed incidentally at process shutdown, causing file descriptor leakage in long-running processes (GH#518)
* Sun Jan 05 2020 Paul Howarth - 1.4.0-1- Update to 1.4.0 (#1787868) - A corner case in #~invoke.context.Context.run# caused overridden streams to be unused if those streams were also set to be hidden, e.g. \'run(command, hide=True, out_stream=StringIO())\' would result in no writes to the \'StringIO\' object (GH#637); this has been fixed - hiding for a given stream is now ignored if that stream has been set to some non-\'None\' (and in the case of \'in_stream\', non-\'False\') value. - As part of feature work on GH#682, we noticed that the \'~invoke.runners.Result\' return value from \'~invoke.context.Context.run\' was inconsistent between dry-run and regular modes; for example, the dry-run version of the object lacked updated values for \'hide\', \'encoding\' and \'env\' - this has been fixed - Add asynchronous behavior to \'~invoke.runners.Runner.run\' (GH#194, GH#682): - Basic asynchronicity, where the method returns as soon as the subprocess has started running, and that return value is an object with methods allowing access to the final result - \"Disowning\" subprocesses entirely, which not only returns immediately but also omits background threading, allowing the subprocesses to outlive Invoke\'s own process See the updated API docs for the \'~invoke.runners.Runner\' for details on the new \'asynchronous\' and \'disown\' kwargs enabling this behavior - Never accompanied the top-level singleton \'~invoke.run\' (which simply wraps an anonymous \'~invoke.context.Context\'s \'run\' method) with its logical sibling, \'~invoke.sudo\' - this has been remedied
* Thu Dec 12 2019 Paul Howarth - 1.3.0-2- Run (most of) the test suite- Cosmetic spec changes
* Mon Oct 07 2019 Othman Madjoudj - 1.3.0-1- Update to 1.3.0 (rhbz #1742597)
* Tue Sep 24 2019 Miro Hrončok - 1.2.0-5- Drop python2-invoke (#1741008)
* Mon Aug 19 2019 Miro Hrončok - 1.2.0-4- Rebuilt for Python 3.8
* Fri Jul 26 2019 Fedora Release Engineering - 1.2.0-3- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
* Thu Jul 11 2019 Othman Madjoudj - 1.2.0-2- Disable tests temporary
* Sat Mar 30 2019 Athmane Madjoudj - 1.2.0-1- Update to 1.2.0 (rhbz #1600756)- Remove upstreamed patches- Add patch for bypass vendorized libs
* Sat Feb 02 2019 Fedora Release Engineering - 1.0.0-4- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild