Scheduled monthly dependency update for April #33

pyup-bot · 2020-04-01T18:09:16Z

Update click from 7.0 to 7.1.1.

Changelog

7.1.1

-------------

Released 2020-03-09

-   Fix ``ClickException`` output going to stdout instead of stderr.
 :issue:`1495`

7.1

-----------

Released 2020-03-09

-   Fix PyPI package name, &quot;click&quot; is lowercase again.
-   Fix link in ``unicode_literals`` error message. :pr:`1151`
-   Add support for colored output on UNIX Jupyter notebooks.
 :issue:`1185`
-   Operations that strip ANSI controls will strip the cursor hide/show
 sequences. :issue:`1216`
-   Remove unused compat shim for ``bytes``. :pr:`1195`
-   Expand testing around termui, especially getchar on Windows.
 :issue:`1116`
-   Fix output on Windows Python 2.7 built with MSVC 14. :pr:`1342`
-   Fix ``OSError`` when running in MSYS2. :issue:`1338`
-   Fix ``OSError`` when redirecting to ``NUL`` stream on Windows.
 :issue:`1065`
-   Fix memory leak when parsing Unicode arguments on Windows.
 :issue:`1136`
-   Fix error in new AppEngine environments. :issue:`1462`
-   Always return one of the passed choices for ``click.Choice``
 :issue:`1277`, :pr:`1318`
-   Add ``no_args_is_help`` option to ``click.Command``, defaults to
 False :pr:`1167`
-   Add ``show_defaults`` parameter to ``Context`` to enable showing
 defaults globally. :issue:`1018`
-   Handle ``env MYPATH=&#39;&#39;`` as though the option were not passed.
 :issue:`1196`
-   It is once again possible to call ``next(bar)`` on an active
 progress bar instance. :issue:`1125`
-   ``open_file`` with ``atomic=True`` retains permissions of existing
 files and respects the current umask for new files. :issue:`1376`
-   When using the test ``CliRunner`` with ``mix_stderr=False``, if
 ``result.stderr`` is empty it will not raise a ``ValueError``.
 :issue:`1193`
-   Remove the unused ``mix_stderr`` parameter from
 ``CliRunner.invoke``. :issue:`1435`
-   Fix ``TypeError`` raised when using bool flags and specifying
 ``type=bool``. :issue:`1287`
-   Newlines in option help text are replaced with spaces before
 re-wrapping to avoid uneven line breaks. :issue:`834`
-   ``MissingParameter`` exceptions are printable in the Python
 interpreter. :issue:`1139`
-   Fix how default values for file-type options are shown during
 prompts. :issue:`914`
-   Fix environment variable automatic generation for commands
 containing ``-``. :issue:`1253`
-   Option help text replaces newlines with spaces when rewrapping, but
 preserves paragraph breaks, fixing multiline formatting.
 :issue:`834, 1066, 1397`
-   Option help text that is wrapped adds an extra newline at the end to
 distinguish it from the next option. :issue:`1075`
-   Consider ``sensible-editor`` when determining the editor to use for
 ``click.edit()``. :pr:`1469`
-   Arguments to system calls such as the executable path passed to
 ``click.edit`` can contains spaces. :pr:`1470`
-   Add ZSH completion autoloading and error handling. :issue:`1348`
-   Add a repr to ``Command``, ``Group``, ``Option``, and ``Argument``,
 showing the name for friendlier debugging. :issue:`1267`
-   Completion doesn&#39;t consider option names if a value starts with
 ``-`` after the ``--`` separator. :issue:`1247`
-   ZSH completion escapes special characters in values. :pr:`1418`
-   Add completion support for Fish shell. :pr:`1423`
-   Decoding bytes option values falls back to UTF-8 in more cases.
 :pr:`1468`
-   Make the warning about old 2-arg parameter callbacks a deprecation
 warning, to be removed in 8.0. This has been a warning since Click
 2.0. :pr:`1492`

Links

PyPI: https://pypi.org/project/click
Changelog: https://pyup.io/changelogs/click/
Homepage: https://palletsprojects.com/p/click/

Update wheel from 0.33.1 to 0.34.2.

Changelog

0.34.2

- Fixed installation of ``wheel`` from sdist on environments without Unicode
file name support

0.34.1

- Fixed installation of ``wheel`` from sdist which was broken due to a chicken
and egg problem with PEP 517 and setuptools_scm

0.34.0

- Dropped Python 3.4 support
- Added automatic platform tag detection for macOS binary wheels
(PR by Grzegorz Bokota)
- Added the ``--compression=`` option to the ``bdist_wheel`` command
- Fixed PyPy tag generation to work with the updated semantics (328)
- Updated project packaging and testing configuration for :pep:`517`
- Moved the contents of setup.py to setup.cfg
- Fixed duplicate RECORD file when using ``wheel pack`` on Windows
- Fixed bdist_wheel failing at cleanup on Windows with a read-only source tree
- Fixed ``wheel pack`` not respecting the existing build tag in ``WHEEL``
- Switched the project to use the &quot;src&quot; layout
- Switched to setuptools_scm_ for versioning

.. _setuptools_scm: https://github.com/pypa/setuptools_scm/

0.33.6

- Fixed regression from 0.33.5 that broke building binary wheels against the
limited ABI
- Fixed egg2wheel compatibility with the future release of Python 3.10
(PR by Anthony Sottile)

0.33.5

- Don&#39;t add the ``m`` ABI flag to wheel names on Python 3.8 (PR by rdb)
- Updated ``MANIFEST.in`` to include many previously omitted files in the sdist

0.33.4

- Reverted PR 289 (adding directory entries to the wheel file) due to
incompatibility with ``distlib.wheel``

0.33.3

- Fixed wheel build failures on some systems due to all attributes being
preserved (PR by Matt Wozniski)

0.33.2

- Fixed empty directories missing from the wheel (PR by Jason R. Coombs)

Links

PyPI: https://pypi.org/project/wheel
Changelog: https://pyup.io/changelogs/wheel/
Repo: https://github.com/pypa/wheel

Update flake8 from 3.7.7 to 3.7.9.

Changelog

3.7.8

-------------------

You can view the `3.7.8 milestone`_ on GitLab for more details.

Bugs Fixed
~~~~~~~~~~

- Fix handling of ``Application.parse_preliminary_options_and_args`` when
argv is an empty list (See also `GitLab!310`_, `GitLab518`_)

- Fix crash when a file parses but fails to tokenize (See also `GitLab!314`_,
`GitLab532`_)

- Log the full traceback on plugin exceptions (See also `GitLab!317`_)

- Fix `` noqa: ...`` comments with multi-letter codes (See also `GitLab!326`_,
`GitLab549`_)


.. all links
.. _3.7.8 milestone:
 https://gitlab.com/pycqa/flake8/milestones/31

.. issue links
.. _GitLab518:
 https://gitlab.com/pycqa/flake8/issues/518
.. _GitLab532:
 https://gitlab.com/pycqa/flake8/issues/532
.. _GitLab549:
 https://gitlab.com/pycqa/flake8/issues/549

.. merge request links
.. _GitLab!310:
 https://gitlab.com/pycqa/flake8/merge_requests/310
.. _GitLab!314:
 https://gitlab.com/pycqa/flake8/merge_requests/314
.. _GitLab!317:
 https://gitlab.com/pycqa/flake8/merge_requests/317
.. _GitLab!326:
 https://gitlab.com/pycqa/flake8/merge_requests/326

Links

PyPI: https://pypi.org/project/flake8
Changelog: https://pyup.io/changelogs/flake8/
Repo: https://gitlab.com/pycqa/flake8

Update tox from 3.7.0 to 3.14.6.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/tox
Docs: http://tox.readthedocs.org

Update coverage from 4.5.2 to 5.0.4.

Changelog

5.0.4

----------------------------

- If using the ``[run] relative_files`` setting, the XML report will use
relative files in the ``&lt;source&gt;`` elements indicating the location of source
code.  Closes `issue 948`_.

- The textual summary report could report missing lines with negative line
numbers on PyPy3 7.1 (`issue 943`_).  This is now fixed.

- Windows wheels for Python 3.8 were incorrectly built, but are now fixed.
(`issue 949`_)

- Updated Python 3.9 support to 3.9a4.

- HTML reports couldn&#39;t be sorted if localStorage wasn&#39;t available. This is now
fixed: sorting works even though the sorting setting isn&#39;t retained. (`issue
944`_ and `pull request 945`_). Thanks, Abdeali Kothari.

.. _issue 943: https://github.com/nedbat/coveragepy/issues/943
.. _issue 944: https://github.com/nedbat/coveragepy/issues/944
.. _pull request 945: https://github.com/nedbat/coveragepy/pull/945
.. _issue 948: https://github.com/nedbat/coveragepy/issues/948
.. _issue 949: https://github.com/nedbat/coveragepy/issues/949


.. _changes_503:

5.0.3

----------------------------

- A performance improvement in 5.0.2 didn&#39;t work for test suites that changed
directory before combining data, causing &quot;Couldn&#39;t use data file: no such
table: meta&quot; errors (`issue 916`_).  This is now fixed.

- Coverage could fail to run your program with some form of &quot;ModuleNotFound&quot; or
&quot;ImportError&quot; trying to import from the current directory. This would happen
if coverage had been packaged into a zip file (for example, on Windows), or
was found indirectly (for example, by pyenv-virtualenv).  A number of
different scenarios were described in `issue 862`_ which is now fixed.  Huge
thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and
George-Cristian Bîrzan for protracted debugging sessions.

- Added the &quot;premain&quot; debug option.

- Added SQLite compile-time options to the &quot;debug sys&quot; output.

.. _issue 862: https://github.com/nedbat/coveragepy/issues/862
.. _issue 916: https://github.com/nedbat/coveragepy/issues/916


.. _changes_502:

5.0.2

----------------------------

- Programs that used multiprocessing and changed directories would fail under
coverage.  This is now fixed (`issue 890`_).  A side effect is that debug
information about the config files read now shows absolute paths to the
files.

- When running programs as modules (``coverage run -m``) with ``--source``,
some measured modules were imported before coverage starts.  This resulted in
unwanted warnings (&quot;Already imported a file that will be measured&quot;) and a
reduction in coverage totals (`issue 909`_).  This is now fixed.

- If no data was collected, an exception about &quot;No data to report&quot; could happen
instead of a 0% report being created (`issue 884`_).  This is now fixed.

- The handling of source files with non-encodable file names has changed.
Previously, if a file name could not be encoded as UTF-8, an error occurred,
as described in `issue 891`_.  Now, those files will not be measured, since
their data would not be recordable.

- A new warning (&quot;dynamic-conflict&quot;) is issued if two mechanisms are trying to
change the dynamic context.  Closes `issue 901`_.

- ``coverage run --debug=sys`` would fail with an AttributeError. This is now
fixed (`issue 907`_).

.. _issue 884: https://github.com/nedbat/coveragepy/issues/884
.. _issue 890: https://github.com/nedbat/coveragepy/issues/890
.. _issue 891: https://github.com/nedbat/coveragepy/issues/891
.. _issue 901: https://github.com/nedbat/coveragepy/issues/901
.. _issue 907: https://github.com/nedbat/coveragepy/issues/907
.. _issue 909: https://github.com/nedbat/coveragepy/issues/909


.. _changes_501:

5.0.1

----------------------------

- If a 4.x data file is the cause of a &quot;file is not a database&quot; error, then use
a more specific error message, &quot;Looks like a coverage 4.x data file, are you
mixing versions of coverage?&quot;  Helps diagnose the problems described in
`issue 886`_.

- Measurement contexts and relative file names didn&#39;t work together, as
reported in `issue 899`_ and `issue 900`_.  This is now fixed, thanks to
David Szotten.

- When using ``coverage run --concurrency=multiprocessing``, all data files
should be named with parallel-ready suffixes.  5.0 mistakenly named the main
process&#39; file with no suffix when using ``--append``.  This is now fixed,
closing `issue 880`_.

- Fixed a problem on Windows when the current directory is changed to a
different drive (`issue 895`_).  Thanks, Olivier Grisel.

- Updated Python 3.9 support to 3.9a2.

.. _issue 880: https://github.com/nedbat/coveragepy/issues/880
.. _issue 886: https://github.com/nedbat/coveragepy/issues/886
.. _issue 895: https://github.com/nedbat/coveragepy/issues/895
.. _issue 899: https://github.com/nedbat/coveragepy/issues/899
.. _issue 900: https://github.com/nedbat/coveragepy/issues/900


.. _changes_50:

5.0

--------------------------

Nothing new beyond 5.0b2.


.. _changes_50b2:

5.0b2

----------------------------

- An experimental ``[run] relative_files`` setting tells coverage to store
relative file names in the data file. This makes it easier to run tests in
one (or many) environments, and then report in another.  It has not had much
real-world testing, so it may change in incompatible ways in the future.

- When constructing a :class:`coverage.Coverage` object, `data_file` can be
specified as None to prevent writing any data file at all.  In previous
versions, an explicit `data_file=None` argument would use the default of
&quot;.coverage&quot;. Fixes `issue 871`_.

- Python files run with ``-m`` now have ``__spec__`` defined properly.  This
fixes `issue 745`_ (about not being able to run unittest tests that spawn
subprocesses), and `issue 838`_, which described the problem directly.

- The ``[paths]`` configuration section is now ordered. If you specify more
than one list of patterns, the first one that matches will be used.  Fixes
`issue 649`_.

- The :func:`.coverage.numbits.register_sqlite_functions` function now also
registers `numbits_to_nums` for use in SQLite queries.  Thanks, Simon
Willison.

- Python 3.9a1 is supported.

- Coverage.py has a mascot: :ref:`Sleepy Snake &lt;sleepy&gt;`.

.. _issue 649: https://github.com/nedbat/coveragepy/issues/649
.. _issue 745: https://github.com/nedbat/coveragepy/issues/745
.. _issue 838: https://github.com/nedbat/coveragepy/issues/838
.. _issue 871: https://github.com/nedbat/coveragepy/issues/871


.. _changes_50b1:

5.0b1

----------------------------

- The HTML and textual reports now have a ``--skip-empty`` option that skips
files with no statements, notably ``__init__.py`` files.  Thanks, Reya B.

- Configuration can now be read from `TOML`_ files.  This requires installing
coverage.py with the ``[toml]`` extra.  The standard &quot;pyproject.toml&quot; file
will be read automatically if no other configuration file is found, with
settings in the ``[tool.coverage.]`` namespace.  Thanks to Frazer McLean for
implementation and persistence.  Finishes `issue 664`_.

- The ``[run] note`` setting has been deprecated. Using it will result in a
warning, and the note will not be written to the data file.  The
corresponding :class:`.CoverageData` methods have been removed.

- The HTML report has been reimplemented (no more table around the source
code). This allowed for a better presentation of the context information,
hopefully resolving `issue 855`_.

- Added sqlite3 module version information to ``coverage debug sys`` output.

- Asking the HTML report to show contexts (``[html] show_contexts=True`` or
``coverage html --show-contexts``) will issue a warning if there were no
contexts measured (`issue 851`_).

.. _TOML: https://github.com/toml-lang/tomlreadme
.. _issue 664: https://github.com/nedbat/coveragepy/issues/664
.. _issue 851: https://github.com/nedbat/coveragepy/issues/851
.. _issue 855: https://github.com/nedbat/coveragepy/issues/855


.. _changes_50a8:

5.0a8

----------------------------

- The :class:`.CoverageData` API has changed how queries are limited to
specific contexts.  Now you use :meth:`.CoverageData.set_query_context` to
set a single exact-match string, or :meth:`.CoverageData.set_query_contexts`
to set a list of regular expressions to match contexts.  This changes the
command-line ``--contexts`` option to use regular expressions instead of
filename-style wildcards.


.. _changes_50a7:

5.0a7

----------------------------

- Data can now be &quot;reported&quot; in JSON format, for programmatic use, as requested
in `issue 720`_.  The new ``coverage json`` command writes raw and summarized
data to a JSON file.  Thanks, Matt Bachmann.

- Dynamic contexts are now supported in the Python tracer, which is important
for PyPy users.  Closes `issue 846`_.

- The compact line number representation introduced in 5.0a6 is called a
&quot;numbits.&quot;  The :mod:`coverage.numbits` module provides functions for working
with them.

- The reporting methods used to permanently apply their arguments to the
configuration of the Coverage object.  Now they no longer do.  The arguments
affect the operation of the method, but do not persist.

- A class named &quot;test_something&quot; no longer confuses the ``test_function``
dynamic context setting.  Fixes `issue 829`_.

- Fixed an unusual tokenizing issue with backslashes in comments.  Fixes
`issue 822`_.

- ``debug=plugin`` didn&#39;t properly support configuration or dynamic context
plugins, but now it does, closing `issue 834`_.

.. _issue 720: https://github.com/nedbat/coveragepy/issues/720
.. _issue 822: https://github.com/nedbat/coveragepy/issues/822
.. _issue 834: https://github.com/nedbat/coveragepy/issues/834
.. _issue 829: https://github.com/nedbat/coveragepy/issues/829
.. _issue 846: https://github.com/nedbat/coveragepy/issues/846


.. _changes_50a6:

5.0a6

----------------------------

- Reporting on contexts. Big thanks to Stephan Richter and Albertas Agejevas
for the contribution.

- The ``--contexts`` option is available on the ``report`` and ``html``
 commands.  It&#39;s a comma-separated list of shell-style wildcards, selecting
 the contexts to report on.  Only contexts matching one of the wildcards
 will be included in the report.

- The ``--show-contexts`` option for the ``html`` command adds context
 information to each covered line.  Hovering over the &quot;ctx&quot; marker at the
 end of the line reveals a list of the contexts that covered the line.

- Database changes:

- Line numbers are now stored in a much more compact way.  For each file and
 context, a single binary string is stored with a bit per line number.  This
 greatly improves memory use, but makes ad-hoc use difficult.

- Dynamic contexts with no data are no longer written to the database.

- SQLite data storage is now faster.  There&#39;s no longer a reason to keep the
 JSON data file code, so it has been removed.

- Changes to the :class:`.CoverageData` interface:

- The new :meth:`.CoverageData.dumps` method serializes the data to a string,
 and a corresponding :meth:`.CoverageData.loads` method reconstitutes this
 data.  The format of the data string is subject to change at any time, and
 so should only be used between two installations of the same version of
 coverage.py.

- The :meth:`CoverageData constructor&lt;.CoverageData.__init__&gt;` has a new
 argument, `no_disk` (default: False).  Setting it to True prevents writing
 any data to the disk.  This is useful for transient data objects.

- Added the classmethod :meth:`.Coverage.current` to get the latest started
Coverage instance.

- Multiprocessing support in Python 3.8 was broken, but is now fixed.  Closes
`issue 828`_.

- Error handling during reporting has changed slightly.  All reporting methods
now behave the same.  The ``--ignore-errors`` option keeps errors from
stopping the reporting, but files that couldn&#39;t parse as Python will always
be reported as warnings.  As with other warnings, you can suppress them with
the ``[run] disable_warnings`` configuration setting.

- Coverage.py no longer fails if the user program deletes its current
directory. Fixes `issue 806`_.  Thanks, Dan Hemberger.

- The scrollbar markers in the HTML report now accurately show the highlighted
lines, regardless of what categories of line are highlighted.

- The hack to accommodate ShiningPanda_ looking for an obsolete internal data
file has been removed, since ShiningPanda 0.22 fixed it four years ago.

- The deprecated `Reporter.file_reporters` property has been removed.

.. _ShiningPanda: https://wiki.jenkins.io/display/JENKINS/ShiningPanda+Plugin
.. _issue 806: https://github.com/nedbat/coveragepy/pull/806
.. _issue 828: https://github.com/nedbat/coveragepy/issues/828


.. _changes_50a5:

5.0a5

----------------------------

- Drop support for Python 3.4

- Dynamic contexts can now be set two new ways, both thanks to Justas
Sadzevičius.

- A plugin can implement a ``dynamic_context`` method to check frames for
 whether a new context should be started.  See
 :ref:`dynamic_context_plugins` for more details.

- Another tool (such as a test runner) can use the new
 :meth:`.Coverage.switch_context` method to explicitly change the context.

- The ``dynamic_context = test_function`` setting now works with Python 2
old-style classes, though it only reports the method name, not the class it
was defined on.  Closes `issue 797`_.

- ``fail_under`` values more than 100 are reported as errors.  Thanks to Mike
Fiedler for closing `issue 746`_.

- The &quot;missing&quot; values in the text output are now sorted by line number, so
that missing branches are reported near the other lines they affect. The
values used to show all missing lines, and then all missing branches.

- Access to the SQLite database used for data storage is now thread-safe.
Thanks, Stephan Richter. This closes `issue 702`_.

- Combining data stored in SQLite is now about twice as fast, fixing `issue
761`_.  Thanks, Stephan Richter.

- The ``filename`` attribute on :class:`.CoverageData` objects has been made
private.  You can use the ``data_filename`` method to get the actual file
name being used to store data, and the ``base_filename`` method to get the
original filename before parallelizing suffixes were added.  This is part of
fixing `issue 708`_.

- Line numbers in the HTML report now align properly with source lines, even
when Chrome&#39;s minimum font size is set, fixing `issue 748`_.  Thanks Wen Ye.

.. _issue 702: https://github.com/nedbat/coveragepy/issues/702
.. _issue 708: https://github.com/nedbat/coveragepy/issues/708
.. _issue 746: https://github.com/nedbat/coveragepy/issues/746
.. _issue 748: https://github.com/nedbat/coveragepy/issues/748
.. _issue 761: https://github.com/nedbat/coveragepy/issues/761
.. _issue 797: https://github.com/nedbat/coveragepy/issues/797


.. _changes_50a4:

5.0a4

----------------------------

- You can specify the command line to run your program with the ``[run]
command_line`` configuration setting, as requested in `issue 695`_.

- Coverage will create directories as needed for the data file if they don&#39;t
exist, closing `issue 721`_.

- The ``coverage run`` command has always adjusted the first entry in sys.path,
to properly emulate how Python runs your program.  Now this adjustment is
skipped if sys.path[0] is already different than Python&#39;s default.  This
fixes `issue 715`_.

- Improvements to context support:

- The &quot;no such table: meta&quot; error is fixed.: `issue 716`_.

- Combining data files is now much faster.

- Python 3.8 (as of today!) passes all tests.

.. _issue 695: https://github.com/nedbat/coveragepy/issues/695
.. _issue 715: https://github.com/nedbat/coveragepy/issues/715
.. _issue 716: https://github.com/nedbat/coveragepy/issues/716
.. _issue 721: https://github.com/nedbat/coveragepy/issues/721


.. _changes_50a3:

5.0a3

----------------------------

- Context support: static contexts let you specify a label for a coverage run,
which is recorded in the data, and retained when you combine files.  See
:ref:`contexts` for more information.

- Dynamic contexts: specifying ``[run] dynamic_context = test_function`` in the
config file will record the test function name as a dynamic context during
execution.  This is the core of &quot;Who Tests What&quot; (`issue 170`_).  Things to
note:

- There is no reporting support yet.  Use SQLite to query the .coverage file
 for information.  Ideas are welcome about how reporting could be extended
 to use this data.

- There&#39;s a noticeable slow-down before any test is run.

- Data files will now be roughly N times larger, where N is the number of
 tests you have.  Combining data files is therefore also N times slower.

- No other values for ``dynamic_context`` are recognized yet.  Let me know
 what else would be useful.  I&#39;d like to use a pytest plugin to get better
 information directly from pytest, for example.

.. _issue 170: https://github.com/nedbat/coveragepy/issues/170

- Environment variable substitution in configuration files now supports two
syntaxes for controlling the behavior of undefined variables: if ``VARNAME``
is not defined, ``${VARNAME?}`` will raise an error, and ``${VARNAME-default
value}`` will use &quot;default value&quot;.

- Partial support for Python 3.8, which has not yet released an alpha. Fixes
`issue 707`_ and `issue 714`_.

.. _issue 707: https://github.com/nedbat/coveragepy/issues/707
.. _issue 714: https://github.com/nedbat/coveragepy/issues/714


.. _changes_50a2:

5.0a2

----------------------------

- Coverage&#39;s data storage has changed.  In version 4.x, .coverage files were
basically JSON.  Now, they are SQLite databases.  This means the data file
can be created earlier than it used to.  A large amount of code was
refactored to support this change.

- Because the data file is created differently than previous releases, you
 may need ``parallel=true`` where you didn&#39;t before.

- The old data format is still available (for now) by setting the environment
 variable COVERAGE_STORAGE=json. Please tell me if you think you need to
 keep the JSON format.

- The database schema is guaranteed to change in the future, to support new
 features.  I&#39;m looking for opinions about making the schema part of the
 public API to coverage.py or not.

- Development moved from `Bitbucket`_ to `GitHub`_.

- HTML files no longer have trailing and extra whitespace.

- The sort order in the HTML report is stored in local storage rather than
cookies, closing `issue 611`_.  Thanks, Federico Bond.

- pickle2json, for converting v3 data files to v4 data files, has been removed.

.. _Bitbucket: https://bitbucket.org/ned/coveragepy
.. _GitHub: https://github.com/nedbat/coveragepy

.. _issue 611: https://github.com/nedbat/coveragepy/issues/611


.. _changes_50a1:

5.0a1

----------------------------

- Coverage.py no longer supports Python 2.6 or 3.3.

- The location of the configuration file can now be specified with a
``COVERAGE_RCFILE`` environment variable, as requested in `issue 650`_.

- Namespace packages are supported on Python 3.7, where they used to cause
TypeErrors about path being None. Fixes `issue 700`_.

- A new warning (``already-imported``) is issued if measurable files have
already been imported before coverage.py started measurement.  See
:ref:`cmd_warnings` for more information.

- Running coverage many times for small runs in a single process should be
faster, closing `issue 625`_.  Thanks, David MacIver.

- Large HTML report pages load faster.  Thanks, Pankaj Pandey.

.. _issue 625: https://bitbucket.org/ned/coveragepy/issues/625/lstat-dominates-in-the-case-of-small
.. _issue 650: https://bitbucket.org/ned/coveragepy/issues/650/allow-setting-configuration-file-location
.. _issue 700: https://github.com/nedbat/coveragepy/issues/700


.. _changes_454:

4.5.4

----------------------------

- Multiprocessing support in Python 3.8 was broken, but is now fixed.  Closes
`issue 828`_.

.. _issue 828: https://github.com/nedbat/coveragepy/issues/828


.. _changes_453:

4.5.3

----------------------------

- Only packaging metadata changes.


.. _changes_452:

Links

PyPI: https://pypi.org/project/coverage
Changelog: https://pyup.io/changelogs/coverage/
Repo: https://github.com/nedbat/coveragepy

Update coveralls from 1.6.0 to 1.11.1.

Changelog

1.11.1

Bug Fixes

* **github:**  rename to github-actions ([9e65a059](9e65a059))
 This fixes a regression introduced with v1.11.0, which may have prevented
 usage of this library on Github Actions.

&lt;a name=&quot;1.11.0&quot;&gt;&lt;/a&gt;

1.11.0

Fixes

* **github:**  add service_number for github actions ([9f93bd8e](9f93bd8e))
 This should fix support for parallel builds.

Compatibility

*  Python 2.7 and 3.4 are now officially End-Of-Life&#39;d. Consider them deprecated
from the perspective of this package -- we&#39;ll remove them in an upcoming
release (likely the first one which requires non-trivial work to continue
supporting them!).

&lt;a name=&quot;1.10.0&quot;&gt;&lt;/a&gt;

1.10.0

Features

*  support coverage&gt;=5.0 (214) ([4a917402](4a917402))

&lt;a name=&quot;1.9.2&quot;&gt;&lt;/a&gt;

1.9.2

Bug Fixes

* **github:**  fixup incorrect API usage (209) ([c338cab4](c338cab4))

&lt;a name=&quot;1.9.1&quot;&gt;&lt;/a&gt;

1.9.1

Compatibility

*  this release marks Python 3.8 as officially supported. Earlier versions probably
supported Python 3.8 too, but now we&#39;re *sure*.

&lt;a name=&quot;1.9.0&quot;&gt;&lt;/a&gt;

1.9.0

Features

* **support:**  support Github Actions CI (207) ([817119c3](817119c3))

Bug Fixes

* **compatibility:**  fixup coverage.__version__ comparisons (208) ([03a57a9a](03a57a9a))

&lt;a name=&quot;1.8.2&quot;&gt;&lt;/a&gt;

1.8.2

Internal

* **dependencies**: update pass urllib3&lt;1.25 pin, now that that&#39;s fixed.

&lt;a name=&quot;1.8.1&quot;&gt;&lt;/a&gt;

1.8.1

Bug Fixes

* **dependencies:**  pin `coverage` to `&lt; 5.0`, since the current `5.0` alphas are
                  introducing breaking changes. Once `5.0` is stable, we&#39;ll
                  remove the pin.

&lt;a name=&quot;1.8.0&quot;&gt;&lt;/a&gt;

1.8.0

Features

* **flag:**  allow disabling SSL verification ([2e3b5c61](2e3b5c61))

Bug Fixes

* **git:**  fix support for case where git binary is missing ([5bbceaae](5bbceaae))

&lt;a name=&quot;1.7.0&quot;&gt;&lt;/a&gt;

1.7.0

Features

* **api:**  support pull requests on buildkite (197) ([2700e3e2](2700e3e2))

Bug Fixes

* **cli:**  ensure upload failures trigger cli failures ([16192b84](16192b84))

&lt;a name=&quot;1.6.0&quot;&gt;&lt;/a&gt;

Links

PyPI: https://pypi.org/project/coveralls
Changelog: https://pyup.io/changelogs/coveralls/
Repo: http://github.com/coveralls-clients/coveralls-python

Update pytest from 4.3.0 to 5.4.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/pytest
Homepage: https://docs.pytest.org/en/latest/

Update pytest-cov from 2.6.1 to 2.8.1.

Changelog

2.8.1

------------------

* Fixed `348 &lt;https://github.com/pytest-dev/pytest-cov/issues/348&gt;`_ -
regression when only certain reports (html or xml) are used then ``--cov-fail-under`` always fails.

2.8.0

------------------

* Fixed ``RecursionError`` that can occur when using
`cleanup_on_signal &lt;https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling&gt;`__ or
`cleanup_on_sigterm &lt;https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling&gt;`__.
See: `294 &lt;https://github.com/pytest-dev/pytest-cov/issues/294&gt;`_.
The 2.7.x releases of pytest-cov should be considered broken regarding aforementioned cleanup API.
* Added compatibility with future xdist release that deprecates some internals
(match pytest-xdist master/worker terminology).
Contributed by Thomas Grainger in `321 &lt;https://github.com/pytest-dev/pytest-cov/pull/321&gt;`_
* Fixed breakage that occurs when multiple reporting options are used.
Contributed by Thomas Grainger in `338 &lt;https://github.com/pytest-dev/pytest-cov/pull/338&gt;`_.
* Changed internals to use a stub instead of ``os.devnull``.
Contributed by Thomas Grainger in `332 &lt;https://github.com/pytest-dev/pytest-cov/pull/332&gt;`_.
* Added support for Coverage 5.0.
Contributed by Ned Batchelder in `319 &lt;https://github.com/pytest-dev/pytest-cov/pull/319&gt;`_.
* Added support for float values in ``--cov-fail-under``.
Contributed by Martín Gaitán in `311 &lt;https://github.com/pytest-dev/pytest-cov/pull/311&gt;`_.
* Various documentation fixes. Contributed by
Juanjo Bazán,
Andrew Murray and
Albert Tugushev in
`298 &lt;https://github.com/pytest-dev/pytest-cov/pull/298&gt;`_,
`299 &lt;https://github.com/pytest-dev/pytest-cov/pull/299&gt;`_ and
`307 &lt;https://github.com/pytest-dev/pytest-cov/pull/307&gt;`_.
* Various testing improvements. Contributed by
Ned Batchelder,
Daniel Hahler,
Ionel Cristian Mărieș and
Hugo van Kemenade in
`313 &lt;https://github.com/pytest-dev/pytest-cov/pull/313&gt;`_,
`314 &lt;https://github.com/pytest-dev/pytest-cov/pull/314&gt;`_,
`315 &lt;https://github.com/pytest-dev/pytest-cov/pull/315&gt;`_,
`316 &lt;https://github.com/pytest-dev/pytest-cov/pull/316&gt;`_,
`325 &lt;https://github.com/pytest-dev/pytest-cov/pull/325&gt;`_,
`326 &lt;https://github.com/pytest-dev/pytest-cov/pull/326&gt;`_,
`334 &lt;https://github.com/pytest-dev/pytest-cov/pull/334&gt;`_ and
`335 &lt;https://github.com/pytest-dev/pytest-cov/pull/335&gt;`_.
* Added the ``--cov-context`` CLI options that enables coverage contexts. Only works with coverage 5.0+.
Contributed by Ned Batchelder in `345 &lt;https://github.com/pytest-dev/pytest-cov/pull/345&gt;`_.

2.7.1

------------------

* Fixed source distribution manifest so that garbage ain&#39;t included in the tarball.

2.7.0

------------------

* Fixed ``AttributeError: &#39;NoneType&#39; object has no attribute &#39;configure_node&#39;`` error when ``--no-cov`` is used.
Contributed by Alexander Shadchin in `263 &lt;https://github.com/pytest-dev/pytest-cov/pull/263&gt;`_.
* Various testing and CI improvements. Contributed by Daniel Hahler in
`255 &lt;https://github.com/pytest-dev/pytest-cov/pull/255&gt;`_,
`266 &lt;https://github.com/pytest-dev/pytest-cov/pull/266&gt;`_,
`272 &lt;https://github.com/pytest-dev/pytest-cov/pull/272&gt;`_,
`271 &lt;https://github.com/pytest-dev/pytest-cov/pull/271&gt;`_ and
`269 &lt;https://github.com/pytest-dev/pytest-cov/pull/269&gt;`_.
* Improved documentation regarding subprocess and multiprocessing.
Contributed in `265 &lt;https://github.com/pytest-dev/pytest-cov/pull/265&gt;`_.
* Improved ``pytest_cov.embed.cleanup_on_sigterm`` to be reentrant (signal deliveries while signal handling is
running won&#39;t break stuff).
* Added ``pytest_cov.embed.cleanup_on_signal`` for customized cleanup.
* Improved cleanup code and fixed various issues with leftover data files. All contributed in
`265 &lt;https://github.com/pytest-dev/pytest-cov/pull/265&gt;`_ or
`262 &lt;https://github.com/pytest-dev/pytest-cov/pull/262&gt;`_.
* Improved examples. Now there are two examples for the common project layouts, complete with working coverage
configuration. The examples have CI testing. Contributed in
`267 &lt;https://github.com/pytest-dev/pytest-cov/pull/267&gt;`_.
* Improved help text for CLI options.

Links

PyPI: https://pypi.org/project/pytest-cov
Changelog: https://pyup.io/changelogs/pytest-cov/
Repo: https://github.com/pytest-dev/pytest-cov

Update pytest-runner from 4.4 to 5.2.

Changelog

5.2

===

* 50: This project is deprecated.

5.1

===

* 49: Surgically restore support for older setuptools versions.

5.0

===

* 42: Prefer pyproject.toml
* Refresh package metadata.
* This release now intentionally introduces the changes
unintionally brought about in 4.5 and 4.3, where the
adoption of declarative config adds a new requirement
on setuptools 30.4 or later. On systems running older
setuptools, installation of pytest-runner via
``easy_install`` (or ``setup_requires``), will result
in a ``DistributionNotFound`` exception.

All projects should pin to ``pytest-runner &lt; 5``
or upgrade the environment to ``setuptools &gt;= 30.4``
(prior to invoking setup.py).

4.5.1

=====

* 48: Revert changes from 4.5 - restoring project to the
state at 4.4.

4.5

===

(Pulled from PyPI due to 43 and 48)

* Packaging (skeleton) refresh, including adoption of
`black &lt;https://pypi.org/project/black&gt;`_ for style.

Links

PyPI: https://pypi.org/project/pytest-runner
Changelog: https://pyup.io/changelogs/pytest-runner/
Repo: https://github.com/pytest-dev/pytest-runner/

Update twine from 1.13.0 to 3.1.1.

Changelog

3.1.1

* :bug:`548` Restore ``--non-interactive`` as a flag not expecting an
argument.

3.1.0

* :feature:`547` Add support for specifying ``--non-interactive`` as an
environment variable.

3.0.0

* :feature:`336` When a client certificate is indicated, all password
processing is disabled.
* :feature:`489` Add ``--non-interactive`` flag to abort upload rather than
interactively prompt if credentials are missing.
* :feature:`524` Twine now unconditionally requires the keyring library
and no longer supports uninstalling ``keyring`` as a means to disable
that functionality. Instead, use ``keyring --disable`` keyring functionality
if necessary.
* :feature:`518` Add Python 3.8 to classifiers.
* :bug:`332 major` More robust handling of server response in
``--skip-existing``

2.0.0

* :feature:`437` Twine now requires Python 3.6 or later. Use pip
9 or pin to &quot;twine&lt;2&quot; to install twine on older Python versions.
* :bug:`491 major` Require requests 2.20 or later to avoid reported security
vulnerabilities in earlier releases.

1.15.0

* :feature:`488` Improved output on ``check`` command:
Prints a message when there are no distributions given to check.
Improved handling of errors in a distribution&#39;s markup, avoiding
messages flowing through to the next distribution&#39;s errors.

1.14.0

* :feature:`456` Better error handling and gpg2 fallback if gpg not available.
* :bug:`341 major` Fail more gracefully when encountering bad metadata
* :feature:`459` Show Warehouse URL after uploading a package
* :feature:`310` Now provide a more meaningful error on redirect during upload.

Links

PyPI: https://pypi.org/project/twine
Changelog: https://pyup.io/changelogs/twine/
Docs: https://twine.readthedocs.io/

coveralls · 2020-04-01T18:10:39Z

Pull Request Test Coverage Report for Build 207

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.106%

Totals
Change from base Build 101:	0.0%
Covered Lines:	80
Relevant Lines:	94

💛 - Coveralls

pyup-bot · 2020-05-01T18:09:19Z

Closing this in favor of #34

pyup-bot added 10 commits April 1, 2020 21:09

Update click from 7.0 to 7.1.1

c7514a6

Update wheel from 0.33.1 to 0.34.2

c2ebd70

Update flake8 from 3.7.7 to 3.7.9

4c9b0da

Update tox from 3.7.0 to 3.14.6

c5d758a

Update coverage from 4.5.2 to 5.0.4

b9d3129

Update coveralls from 1.6.0 to 1.11.1

a1e1977

Update pytest from 4.3.0 to 5.4.1

3f671a2

Update pytest-cov from 2.6.1 to 2.8.1

6626fb9

Update pytest-runner from 4.4 to 5.2

1a83737

Update twine from 1.13.0 to 3.1.1

9576305

pyup-bot mentioned this pull request Apr 1, 2020

Scheduled monthly dependency update for March #32

Closed

pyup-bot closed this May 1, 2020

Orhideous deleted the pyup-scheduled-update-2020-04-01 branch May 1, 2020 18:09

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Scheduled monthly dependency update for April #33

Scheduled monthly dependency update for April #33

Uh oh!

pyup-bot commented Apr 1, 2020

Uh oh!

coveralls commented Apr 1, 2020 •

edited

Loading

Uh oh!

pyup-bot commented May 1, 2020

Uh oh!

Uh oh!

Scheduled monthly dependency update for April #33

Scheduled monthly dependency update for April #33

Uh oh!

Conversation

pyup-bot commented Apr 1, 2020

Update click from 7.0 to 7.1.1.

7.1.1

7.1

Update wheel from 0.33.1 to 0.34.2.

0.34.2

0.34.1

0.34.0

0.33.6

0.33.5

0.33.4

0.33.3

0.33.2

Update flake8 from 3.7.7 to 3.7.9.

3.7.8

Update tox from 3.7.0 to 3.14.6.

Update coverage from 4.5.2 to 5.0.4.

5.0.4

5.0.3

5.0.2

5.0.1

5.0

5.0b2

5.0b1

5.0a8

5.0a7

5.0a6

5.0a5

5.0a4

5.0a3

5.0a2

5.0a1

4.5.4

4.5.3

Update coveralls from 1.6.0 to 1.11.1.

1.11.1

1.11.0

1.10.0

1.9.2

1.9.1

1.9.0

1.8.2

1.8.1

1.8.0

1.7.0

Update pytest from 4.3.0 to 5.4.1.

Update pytest-cov from 2.6.1 to 2.8.1.

2.8.1

2.8.0

2.7.1

2.7.0

Update pytest-runner from 4.4 to 5.2.

5.2

5.1

5.0

4.5.1

4.5

Update twine from 1.13.0 to 3.1.1.

3.1.1

3.1.0

3.0.0

2.0.0

1.15.0

1.14.0

Uh oh!

coveralls commented Apr 1, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Test Coverage Report for Build 207

💛 - Coveralls

Uh oh!

pyup-bot commented May 1, 2020

Uh oh!

Uh oh!

coveralls commented Apr 1, 2020 •

edited

Loading