Coverage remained the same at 96.659% when pulling 221f1b8966e878cb6ba1a2ff82f44d5b5e09aeb7 on pyup-update-future-0.16.0-to-0.17.0 into bb0e3ac6b2d4e8b4f33e304469976720e9e1351f on master.
Coverage remained the same at 96.659% when pulling 221f1b8966e878cb6ba1a2ff82f44d5b5e09aeb7 on pyup-update-future-0.16.0-to-0.17.0 into bb0e3ac6b2d4e8b4f33e304469976720e9e1351f on master.
Coverage remained the same at 96.659% when pulling 221f1b8966e878cb6ba1a2ff82f44d5b5e09aeb7 on pyup-update-future-0.16.0-to-0.17.0 into bb0e3ac6b2d4e8b4f33e304469976720e9e1351f on master.
Coverage remained the same at 96.659% when pulling 221f1b8966e878cb6ba1a2ff82f44d5b5e09aeb7 on pyup-update-future-0.16.0-to-0.17.0 into bb0e3ac6b2d4e8b4f33e304469976720e9e1351f on master.
This PR updates future from 0.16.0 to 0.17.0.
The bot wasn't able to find a changelog for this release. Got an idea?
Links
- PyPI: https://pypi.org/project/future - Changelog: https://pyup.io/changelogs/future/ - Homepage: https://python-future.org - Docs: https://pythonhosted.org/future/