Initial Update

[pyup-bot]

This is my first visit to this fine repo so I have bundled all updates in a single pull request to make things easier for you to merge.

Close this pull request and delete the branch if you want me to start with single pull requests right away

Here's the executive summary:

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

coverage	4.2	»	4.3.4	PyPI | Changelog | Docs
docutils	0.12	»	0.13.1	PyPI | Homepage
flake8	3.2.1	»	3.3.0	PyPI | Repo
pycodestyle	2.2.0	»	2.3.1	PyPI | Changelog | Docs
pyflakes	1.3.0	»	1.5.0	PyPI | Changelog | Repo
pytest	3.0.5	»	3.0.6	PyPI | Changelog | Homepage
pytest-sugar	0.7.1	»	0.8.0	PyPI | Changelog | Homepage
Pygments	2.1.3	»	2.2.0	PyPI | Changelog | Homepage

Changelogs

coverage 4.2 -> 4.3.4

4.3.4

---

• Fixing 2.6 in version 4.3.3 broke other things, because the too-tricky
  exception wasn't properly derived from Exception, described in issue 556_.
  A newb mistake; it hasn't been a good few days.

.. _issue 556: https://bitbucket.org/ned/coveragepy/issues/556/43-fails-if-there-are-html-files-in-the

.. _changes_433:

4.3.3

---

• Python 2.6 support was broken due to a testing exception imported for the
  benefit of the coverage.py test suite. Properly conditionalizing it fixed
  issue 554_ so that Python 2.6 works again.

.. _issue 554: https://bitbucket.org/ned/coveragepy/issues/554/traceback-on-python-26-starting-with-432

.. _changes_432:

4.3.2

---

• Using the --skip-covered option on an HTML report with 100% coverage
  would cause a "No data to report" error, as reported in issue 549_. This is
  now fixed; thanks, Loïc Dachary.

• If-statements can be optimized away during compilation, for example, if 0:
  or if __debug__:. Coverage.py had problems properly understanding these
  statements which existed in the source, but not in the compiled bytecode.
  This problem, reported in issue 522_, is now fixed.

• If you specified --source as a directory, then coverage.py would look for
  importable Python files in that directory, and could identify ones that had
  never been executed at all. But if you specified it as a package name, that
  detection wasn't performed. Now it is, closing issue 426_. Thanks to Loïc
  Dachary for the fix.

• If you started and stopped coverage measurement thousands of times in your
  process, you could crash Python with a "Fatal Python error: deallocating
  None" error. This is now fixed. Thanks to Alex Groce for the bug report.

• On PyPy, measuring coverage in subprocesses could produce a warning: "Trace
  function changed, measurement is likely wrong: None". This was spurious, and
  has been suppressed.

• Previously, coverage.py couldn't start on Jython, due to that implementation
  missing the multiprocessing module (issue 551). This problem has now been
  fixed. Also, issue 322 about not being able to invoke coverage
  conveniently, seems much better: jython -m coverage run myprog.py works
  properly.

• Let's say you ran the HTML report over and over again in the same output
  directory, with --skip-covered. And imagine due to your heroic
  test-writing efforts, a file just acheived the goal of 100% coverage. With
  coverage.py 4.3, the old HTML file with the less-than-100% coverage would be
  left behind. This file is now properly deleted.

.. _issue 322: https://bitbucket.org/ned/coveragepy/issues/322/cannot-use-coverage-with-jython
.. issue 426: https://bitbucket.org/ned/coveragepy/issues/426/difference-between-coverage-results-with
.. issue 522: https://bitbucket.org/ned/coveragepy/issues/522/incorrect-branch-reporting-with-__debug
.. _issue 549: https://bitbucket.org/ned/coveragepy/issues/549/skip-covered-with-100-coverage-throws-a-no
.. _issue 551: https://bitbucket.org/ned/coveragepy/issues/551/coveragepy-cannot-be-imported-in-jython27

.. _changes_431:

4.3.1

---

• Some environments couldn't install 4.3, as described in issue 540_. This is
  now fixed.

• The check for conflicting --source and --include was too simple in a
  few different ways, breaking a few perfectly reasonable use cases, described
  in issue 541. The check has been reverted while we re-think the fix for
  issue 265.

.. _issue 540: https://bitbucket.org/ned/coveragepy/issues/540/cant-install-coverage-v43-into-under
.. _issue 541: https://bitbucket.org/ned/coveragepy/issues/541/coverage-43-breaks-nosetest-with-coverage

.. _changes_43:

4.3

---

Special thanks to Loïc Dachary, who took an extraordinary interest in
coverage.py and contributed a number of improvements in this release.

• Subprocesses that are measured with automatic subprocess measurement_ used
  to read in any pre-existing data file. This meant data would be incorrectly
  carried forward from run to run. Now those files are not read, so each
  subprocess only writes its own data. Fixes issue 510_.

• The coverage combine command will now fail if there are no data files to
  combine. The combine changes in 4.2 meant that multiple combines could lose
  data, leaving you with an empty .coverage data file. Fixes
  issue 525, issue 412, issue 516, and probably issue 511.

• Coverage.py wouldn't execute sys.excepthook_ when an exception happened in
  your program. Now it does, thanks to Andrew Hoos. Closes issue 535_.

• Branch coverage fixes:

• Branch coverage could misunderstand a finally clause on a try block that
  never continued on to the following statement, as described in issue 493_. This is now fixed. Thanks to Joe Doherty for the report and Loïc
  Dachary for the fix.

• A while loop with a constant condition (while True) and a continue
  statement would be mis-analyzed, as described in issue 496_. This is now
  fixed, thanks to a bug report by Eli Skeggs and a fix by Loïc Dachary.

• While loops with constant conditions that were never executed could result
  in a non-zero coverage report. Artem Dayneko reported this in issue 502_, and Loïc Dachary provided the fix.

• The HTML report now supports a --skip-covered option like the other
  reporting commands. Thanks, Loïc Dachary for the implementation, closing
  issue 433_.

• Options can now be read from a tox.ini file, if any. Like setup.cfg, sections
  are prefixed with "coverage:", so [run] options will be read from the
  [coverage:run] section of tox.ini. Implements part of issue 519_.
  Thanks, Stephen Finucane.

• Specifying both --source and --include no longer silently ignores the
  include setting, instead it fails with a message. Thanks, Nathan Land and
  Loïc Dachary. Closes issue 265_.

• The Coverage.combine method has a new parameter, strict=False, to
  support failing if there are no data files to combine.

• When forking subprocesses, the coverage data files would have the same random
  number appended to the file name. This didn't cause problems, because the
  file names had the process id also, making collisions (nearly) impossible.
  But it was disconcerting. This is now fixed.

• The text report now properly sizes headers when skipping some files, fixing
  issue 524_. Thanks, Anthony Sottile and Loïc Dachary.

• Coverage.py can now search .pex files for source, just as it can .zip and
  .egg. Thanks, Peter Ebden.

• Data files are now about 15% smaller.

• Improvements in the [run] debug setting:

• The "dataio" debug setting now also logs when data files are deleted during
  combining or erasing.

• A new debug option, "multiproc", for logging the behavior of
  concurrency=multiprocessing.

• If you used the debug options "config" and "callers" together, you'd get a
  call stack printed for every line in the multi-line config output. This is
  now fixed.

• Fixed an unusual bug involving multiple coding declarations affecting code
  containing code in multi-line strings: issue 529_.

• Coverage.py will no longer be misled into thinking that a plain file is a
  package when interpreting --source options. Thanks, Cosimo Lupo.

• If you try to run a non-Python file with coverage.py, you will now get a more
  useful error message. Issue 514_.

• The default pragma regex changed slightly, but this will only matter to you
  if you are deranged and use mixed-case pragmas.

• Deal properly with non-ASCII file names in an ASCII-only world, issue 533_.

• Programs that set Unicode configuration values could cause UnicodeErrors when
  generating HTML reports. Pytest-cov is one example. This is now fixed.

• Prevented deprecation warnings from configparser that happened in some
  circumstances, closing issue 530_.

• Corrected the name of the jquery.ba-throttle-debounce.js library. Thanks,
  Ben Finney. Closes issue 505_.

• Testing against PyPy 5.6 and PyPy3 5.5.

• Switched to pytest from nose for running the coverage.py tests.

• Renamed AUTHORS.txt to CONTRIBUTORS.txt, since there are other ways to
  contribute than by writing code. Also put the count of contributors into the
  author string in setup.py, though this might be too cute.

.. _sys.excepthook: https://docs.python.org/3/library/sys.htmlsys.excepthook
.. _issue 265: https://bitbucket.org/ned/coveragepy/issues/265/when-using-source-include-is-silently
.. _issue 412: https://bitbucket.org/ned/coveragepy/issues/412/coverage-combine-should-error-if-no
.. _issue 433: https://bitbucket.org/ned/coveragepy/issues/433/coverage-html-does-not-suport-skip-covered
.. _issue 493: https://bitbucket.org/ned/coveragepy/issues/493/confusing-branching-failure
.. _issue 496: https://bitbucket.org/ned/coveragepy/issues/496/incorrect-coverage-with-branching-and
.. _issue 502: https://bitbucket.org/ned/coveragepy/issues/502/incorrect-coverage-report-with-cover
.. _issue 505: https://bitbucket.org/ned/coveragepy/issues/505/use-canonical-filename-for-debounce
.. _issue 514: https://bitbucket.org/ned/coveragepy/issues/514/path-to-problem-file-not-reported-when
.. _issue 510: https://bitbucket.org/ned/coveragepy/issues/510/erase-still-needed-in-42
.. _issue 511: https://bitbucket.org/ned/coveragepy/issues/511/version-42-coverage-combine-empties
.. _issue 516: https://bitbucket.org/ned/coveragepy/issues/516/running-coverage-combine-twice-deletes-all
.. _issue 519: https://bitbucket.org/ned/coveragepy/issues/519/coverage-run-sections-in-toxini-or-as
.. _issue 524: https://bitbucket.org/ned/coveragepy/issues/524/coverage-report-with-skip-covered-column
.. _issue 525: https://bitbucket.org/ned/coveragepy/issues/525/coverage-combine-when-not-in-parallel-mode
.. _issue 529: https://bitbucket.org/ned/coveragepy/issues/529/encoding-marker-may-only-appear-on-the
.. _issue 530: https://bitbucket.org/ned/coveragepy/issues/530/deprecationwarning-you-passed-a-bytestring
.. _issue 533: https://bitbucket.org/ned/coveragepy/issues/533/exception-on-unencodable-file-name
.. _issue 535: https://bitbucket.org/ned/coveragepy/issues/535/sysexcepthook-is-not-called

.. _changes_42:

pycodestyle 2.2.0 -> 2.3.1

2.3.0

---

New Checks:

• Add E722 warning for bare except clauses
• Report E704 for async function definitions (async def)

Bugs:

• Fix another E305 false positive for variables beginning with "class" or
  "def"
• Fix detection of multiple spaces betwen async and def
• Fix handling of variable annotations. Stop reporting E701 on Python 3.6 for
  variable annotations.

pyflakes 1.3.0 -> 1.5.0

1.4.0

• Change formatting of ImportStarMessage to be consistent with other errors
• Support PEP 498 "f-strings"

pytest 3.0.5 -> 3.0.6

3.0.6.dev0

=======================

• pytest no longer generates PendingDeprecationWarning from its own operations, which was introduced by mistake in version 3.0.5 (2118).
  Thanks to nicoddemus for the report and RonnyPfannschmidt_ for the PR.

• pytest no longer recognizes coroutine functions as yield tests (2129).
  Thanks to malinoff for the PR.

• Plugins loaded by the PYTEST_PLUGINS environment variable are now automatically
  considered for assertion rewriting (2185).
  Thanks nicoddemus for the PR.

• Improve error message when pytest.warns fails (2150). The type(s) of the
  expected warnings and the list of caught warnings is added to the
  error message. Thanks lesteve for the PR.

• Fix pytester internal plugin to work correctly with latest versions of
  zope.interface (1989). Thanks nicoddemus for the PR.

• Assert statements of the pytester plugin again benefit from assertion rewriting (1920).
  Thanks RonnyPfannschmidt for the report and nicoddemus_ for the PR.

• Specifying tests with colons like test_foo.py::test_bar for tests in
  subdirectories with ini configuration files now uses the correct ini file
  (2148). Thanks pelme.

• Fail testdir.runpytest().assert_outcomes() explicitly if the pytest
  terminal output it relies on is missing. Thanks to eli-b_ for the PR.

.. _lesteve: https://github.com/lesteve
.. _malinoff: https://github.com/malinoff
.. _pelme: https://github.com/pelme
.. _eli-b: https://github.com/eli-b

.. _2118: pytest-dev/pytest#2118

.. _1989: pytest-dev/pytest#1989
.. _1920: pytest-dev/pytest#1920
.. _2129: pytest-dev/pytest#2129
.. _2148: pytest-dev/pytest#2148
.. _2150: pytest-dev/pytest#2150
.. _2185: pytest-dev/pytest#2185

pytest-sugar 0.7.1 -> 0.8.0

0.8.0

^^^^^^^^^^^^^^^^^^^

• Release as an universal wheel
• Pytest3 compatibility
• Treat setup/teardown failures as errors
• Fix path issue in --new-summary
• Disable sugar output when not in terminal, should help with testing other pytest plugins
• Add double colons when in verbose mode
• Make --new-summary default, replaced flag with --old-summary

Pygments 2.1.3 -> 2.2.0

2.2

---

(in development)

• Added lexers:

• AMPL
• TypoScript (1173)
• Varnish config (PR554)
• Clean (PR503)
• WDiff (PR513)
• Flatline (PR551)
• Silver (PR537)
• HSAIL (PR518)
• JSGF (PR546)
• NCAR command language (PR536)
• Extempore (PR530)
• Cap'n Proto (PR595)
• Whiley (PR573)
• Monte (PR592)
• Crystal (PR576)
• Snowball (PR589)
• CapDL (PR579)
• NuSMV (PR564)
• SAS, Stata (PR593)

• Added the ability to load lexer and formatter classes directly from files
  with the -x command line option and the lexers.load_lexer_from_file()
  and formatters.load_formatter_from_file() functions. (PR559)

• Added lexers.find_lexer_class_by_name(). (1203)

• Added new token types and lexing for magic methods and variables in Python
  and PHP.

• Added a new token type for string affixes and lexing for them in Python, C++
  and Postgresql lexers.

• Added a new token type for heredoc (and similar) string delimiters and
  lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers.

• Styles can now define colors with ANSI colors for use in the 256-color
  terminal formatter. (PR531)

• Improved the CSS lexer. (1083, 1130)

• Added "Rainbow Dash" style. (PR623)

• Delay loading pkg_resources, which takes a long while to import. (PR690)

Once you have closed this pull request, I'll create seperate pull requests for every update as soon as I find them.

That's it for now!

Happy merging! 🤖

[codecov-io]

Codecov Report

Merging #1 into master will increase coverage by 1.55%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master     #1      +/-   ##
========================================
+ Coverage   98.45%   100%   +1.55%     
========================================
  Files           3      3              
  Lines         129    172      +43     
  Branches       20     39      +19     
========================================
+ Hits          127    172      +45     
+ Misses          1      0       -1     
+ Partials        1      0       -1

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b33c27...3b4652f. Read the comment docs.