Scheduled monthly dependency update for February #48

pyup-bot · 2020-02-01T15:34:19Z

Update setuptools from 41.6.0 to 45.1.0.

Changelog

45.1.0

-------

* 1458: Add minimum sunset date and preamble to Python 2 warning.
* 1704: Set sys.argv[0] in setup script run by build_meta.__legacy__
* 1974: Add Python 3 Only Trove Classifier and remove universal wheel declaration for more complete transition from Python 2.

45.0.0

-------

* 1458: Drop support for Python 2. Setuptools now requires Python 3.5 or later. Install setuptools using pip &gt;=9 or pin to Setuptools &lt;45 to maintain 2.7 support.
* 1959: Fix for Python 4: replace unsafe six.PY3 with six.PY2

44.0.0

-------

* 1908: Drop support for Python 3.4.

43.0.0

-------

* 1634: Include ``pyproject.toml`` in source distribution by default. Projects relying on the previous behavior where ``pyproject.toml`` was excluded by default should stop relying on that behavior or add ``exclude pyproject.toml`` to their MANIFEST.in file.
* 1927: Setuptools once again declares &#39;setuptools&#39; in the ``build-system.requires`` and adds PEP 517 build support by declaring itself as the ``build-backend``. It additionally specifies ``build-system.backend-path`` to rely on itself for those builders that support it.

42.0.2

-------

* 1921: Fix support for easy_install&#39;s ``find-links`` option in ``setup.cfg``.
* 1922: Build dependencies (setup_requires and tests_require) now install transitive dependencies indicated by extras.

42.0.1

-------

* 1918: Fix regression in handling wheels compatibility tags.

42.0.0

-------

* 1830, 1909: Mark the easy_install script and setuptools command as deprecated, and use `pip &lt;https://pip.pypa.io/en/stable/&gt;`_ when available to fetch/build wheels for missing ``setup_requires``/``tests_require`` requirements, with the following differences in behavior:
* support for ``python_requires``
* better support for wheels (proper handling of priority with respect to PEP 425 tags)
* PEP 517/518 support
* eggs are not supported
* no support for the ``allow_hosts`` easy_install option (``index_url``/``find_links`` are still honored)
* pip environment variables are honored (and take precedence over easy_install options)
* 1898: Removed the &quot;upload&quot; and &quot;register&quot; commands in favor of `twine &lt;https://pypi.org/p/twine&gt;`_.
* 1767: Add support for the ``license_files`` option in ``setup.cfg`` to automatically
include multiple license files in a source distribution.
* 1829: Update handling of wheels compatibility tags:
* add support for manylinux2010
* fix use of removed &#39;m&#39; ABI flag in Python 3.8 on Windows
* 1861: Fix empty namespace package installation from wheel.
* 1877: Setuptools now exposes a new entry point hook &quot;setuptools.finalize_distribution_options&quot;, enabling plugins like `setuptools_scm &lt;https://pypi.org/project/setuptools_scm&gt;`_ to configure options on the distribution at finalization time.

Links

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

Update pip from 19.3.1 to 20.0.2.

Changelog

20.0.2

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

Bug Fixes
---------

- Fix a regression in generation of compatibility tags. (`7626 &lt;https://github.com/pypa/pip/issues/7626&gt;`_)

Vendored Libraries
------------------

- Upgrade packaging to 20.1

20.0.1

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

Bug Fixes
---------

- Rename an internal module, to avoid ImportErrors due to improper uninstallation. (`7621 &lt;https://github.com/pypa/pip/issues/7621&gt;`_)

20.0

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

Process
-------

- Switch to a dedicated CLI tool for vendoring dependencies.

Deprecations and Removals
-------------------------

- Remove wheel tag calculation from pip and use ``packaging.tags``. This
should provide more tags ordered better than in prior releases. (`6908 &lt;https://github.com/pypa/pip/issues/6908&gt;`_)
- Deprecate setup.py-based builds that do not generate an ``.egg-info`` directory. (`6998 &lt;https://github.com/pypa/pip/issues/6998&gt;`_)
- The pip&gt;=20 wheel cache is not retro-compatible with previous versions. Until
pip 21.0, pip will continue to take advantage of existing legacy cache
entries. (`7296 &lt;https://github.com/pypa/pip/issues/7296&gt;`_)
- Deprecate undocumented ``--skip-requirements-regex`` option. (`7297 &lt;https://github.com/pypa/pip/issues/7297&gt;`_)
- Deprecate passing install-location-related options via ``--install-option``. (`7309 &lt;https://github.com/pypa/pip/issues/7309&gt;`_)
- Use literal &quot;abi3&quot; for wheel tag on CPython 3.x, to align with PEP 384
which only defines it for this platform. (`7327 &lt;https://github.com/pypa/pip/issues/7327&gt;`_)
- Remove interpreter-specific major version tag e.g. ``cp3-none-any``
from consideration. This behavior was not documented strictly, and this
tag in particular is `not useful &lt;https://snarky.ca/the-challenges-in-designing-a-library-for-pep-425/&gt;`_.
Anyone with a use case can create an issue with pypa/packaging. (`7355 &lt;https://github.com/pypa/pip/issues/7355&gt;`_)
- Wheel processing no longer permits wheels containing more than one top-level
.dist-info directory. (`7487 &lt;https://github.com/pypa/pip/issues/7487&gt;`_)
- Support for the ``git+git`` form of VCS requirement is being deprecated and
will be removed in pip 21.0. Switch to ``git+https://`` or
``git+ssh://``. ``git+git://`` also works but its use is discouraged as it is
insecure. (`7543 &lt;https://github.com/pypa/pip/issues/7543&gt;`_)

Features
--------

- Default to doing a user install (as if ``--user`` was passed) when the main
site-packages directory is not writeable and user site-packages are enabled. (`1668 &lt;https://github.com/pypa/pip/issues/1668&gt;`_)
- Warn if a path in PATH starts with tilde during ``pip install``. (`6414 &lt;https://github.com/pypa/pip/issues/6414&gt;`_)
- Cache wheels built from Git requirements that are considered immutable,
because they point to a commit hash. (`6640 &lt;https://github.com/pypa/pip/issues/6640&gt;`_)
- Add option ``--no-python-version-warning`` to silence warnings
related to deprecation of Python versions. (`6673 &lt;https://github.com/pypa/pip/issues/6673&gt;`_)
- Cache wheels that ``pip wheel`` built locally, matching what
``pip install`` does. This particularly helps performance in workflows where
``pip wheel`` is used for `building before installing
&lt;https://pip.pypa.io/en/stable/user_guide/installing-from-local-packages&gt;`_.
Users desiring the original behavior can use ``pip wheel --no-cache-dir``. (`6852 &lt;https://github.com/pypa/pip/issues/6852&gt;`_)
- Display CA information in ``pip debug``. (`7146 &lt;https://github.com/pypa/pip/issues/7146&gt;`_)
- Show only the filename (instead of full URL), when downloading from PyPI. (`7225 &lt;https://github.com/pypa/pip/issues/7225&gt;`_)
- Suggest a more robust command to upgrade pip itself to avoid confusion when the
current pip command is not available as ``pip``. (`7376 &lt;https://github.com/pypa/pip/issues/7376&gt;`_)
- Define all old pip console script entrypoints to prevent import issues in
stale wrapper scripts. (`7498 &lt;https://github.com/pypa/pip/issues/7498&gt;`_)
- The build step of ``pip wheel`` now builds all wheels to a cache first,
then copies them to the wheel directory all at once.
Before, it built them to a temporary direcory and moved
them to the wheel directory one by one. (`7517 &lt;https://github.com/pypa/pip/issues/7517&gt;`_)
- Expand ``~`` prefix to user directory in path options, configs, and
environment variables. Values that may be either URL or path are not
currently supported, to avoid ambiguity:

* ``--find-links``
* ``--constraint``, ``-c``
* ``--requirement``, ``-r``
* ``--editable``, ``-e`` (`980 &lt;https://github.com/pypa/pip/issues/980&gt;`_)

Bug Fixes
---------

- Correctly handle system site-packages, in virtual environments created with venv (PEP 405). (`5702 &lt;https://github.com/pypa/pip/issues/5702&gt;`_, `7155 &lt;https://github.com/pypa/pip/issues/7155&gt;`_)
- Fix case sensitive comparison of pip freeze when used with -r option. (`5716 &lt;https://github.com/pypa/pip/issues/5716&gt;`_)
- Enforce PEP 508 requirement format in ``pyproject.toml``
``build-system.requires``. (`6410 &lt;https://github.com/pypa/pip/issues/6410&gt;`_)
- Make ``ensure_dir()`` also ignore ``ENOTEMPTY`` as seen on Windows. (`6426 &lt;https://github.com/pypa/pip/issues/6426&gt;`_)
- Fix building packages which specify ``backend-path`` in pyproject.toml. (`6599 &lt;https://github.com/pypa/pip/issues/6599&gt;`_)
- Do not attempt to run ``setup.py clean`` after a ``pep517`` build error,
since a ``setup.py`` may not exist in that case. (`6642 &lt;https://github.com/pypa/pip/issues/6642&gt;`_)
- Fix passwords being visible in the index-url in
&quot;Downloading &lt;url&gt;&quot; message. (`6783 &lt;https://github.com/pypa/pip/issues/6783&gt;`_)
- Change method from shutil.remove to shutil.rmtree in noxfile.py. (`7191 &lt;https://github.com/pypa/pip/issues/7191&gt;`_)
- Skip running tests which require subversion, when svn isn&#39;t installed (`7193 &lt;https://github.com/pypa/pip/issues/7193&gt;`_)
- Fix not sending client certificates when using ``--trusted-host``. (`7207 &lt;https://github.com/pypa/pip/issues/7207&gt;`_)
- Make sure ``pip wheel`` never outputs pure python wheels with a
python implementation tag. Better fix/workaround for
`3025 &lt;https://github.com/pypa/pip/issues/3025&gt;`_ by
using a per-implementation wheel cache instead of caching pure python
wheels with an implementation tag in their name. (`7296 &lt;https://github.com/pypa/pip/issues/7296&gt;`_)
- Include ``subdirectory`` URL fragments in cache keys. (`7333 &lt;https://github.com/pypa/pip/issues/7333&gt;`_)
- Fix typo in warning message when any of ``--build-option``, ``--global-option``
and ``--install-option`` is used in requirements.txt (`7340 &lt;https://github.com/pypa/pip/issues/7340&gt;`_)
- Fix the logging of cached HTTP response shown as downloading. (`7393 &lt;https://github.com/pypa/pip/issues/7393&gt;`_)
- Effectively disable the wheel cache when it is not writable, as is the
case with the http cache. (`7488 &lt;https://github.com/pypa/pip/issues/7488&gt;`_)
- Correctly handle relative cache directory provided via --cache-dir. (`7541 &lt;https://github.com/pypa/pip/issues/7541&gt;`_)

Vendored Libraries
------------------

- Upgrade CacheControl to 0.12.5
- Upgrade certifi to 2019.9.11
- Upgrade colorama to 0.4.1
- Upgrade distlib to 0.2.9.post0
- Upgrade ipaddress to 1.0.22
- Update packaging to 20.0.
- Upgrade pkg_resources (via setuptools) to 44.0.0
- Upgrade pyparsing to 2.4.2
- Upgrade six to 1.12.0
- Upgrade urllib3 to 1.25.6

Improved Documentation
----------------------

- Document that &quot;coding: utf-8&quot; is supported in requirements.txt (`7182 &lt;https://github.com/pypa/pip/issues/7182&gt;`_)
- Explain how to get pip&#39;s source code in `Getting Started &lt;https://pip.pypa.io/en/stable/development/getting-started/&gt;`_ (`7197 &lt;https://github.com/pypa/pip/issues/7197&gt;`_)
- Describe how basic authentication credentials in URLs work. (`7201 &lt;https://github.com/pypa/pip/issues/7201&gt;`_)
- Add more clear installation instructions (`7222 &lt;https://github.com/pypa/pip/issues/7222&gt;`_)
- Fix documentation links for index options (`7347 &lt;https://github.com/pypa/pip/issues/7347&gt;`_)
- Better document the requirements file format (`7385 &lt;https://github.com/pypa/pip/issues/7385&gt;`_)

Links

PyPI: https://pypi.org/project/pip
Changelog: https://pyup.io/changelogs/pip/
Homepage: https://pip.pypa.io/

Update pydocstyle from 4.0.1 to 5.0.2.

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

Links

PyPI: https://pypi.org/project/pydocstyle
Changelog: https://pyup.io/changelogs/pydocstyle/
Repo: https://github.com/PyCQA/pydocstyle/

Update virtualenv from 16.7.7 to 16.7.9.

Changelog

16.7.9

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

Bugfixes
^^^^^^^^

- upgrade setuptools from ``41.6.0`` to ``42.0.2`` (`1460 &lt;https://github.com/pypa/virtualenv/issues/1460&gt;`_)

16.7.8

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

Bugfixes
^^^^^^^^

- upgrade setuptools from 41.4.0 to 41.6.0 (`1442 &lt;https://github.com/pypa/virtualenv/issues/1442&gt;`_)

Links

PyPI: https://pypi.org/project/virtualenv
Changelog: https://pyup.io/changelogs/virtualenv/
Homepage: https://virtualenv.pypa.io/

Update coverage from 4.5.4 to 5.0.3.

Changelog

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:

Links

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

Update tox from 3.14.0 to 3.14.3.

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 coveralls from 1.8.2 to 1.10.0.

Changelog

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;

Links

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

claassistantio · 2020-02-01T15:35:22Z

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

pyup-bot added 8 commits February 1, 2020 11:34

Update setuptools from 41.6.0 to 45.1.0

3f31b2b

Update setuptools from 41.6.0 to 45.1.0

b449c2e

Update pip from 19.3.1 to 20.0.2

783de25

Update pydocstyle from 4.0.1 to 5.0.2

4f0059f

Update virtualenv from 16.7.7 to 16.7.9

9f5ba82

Update coverage from 4.5.4 to 5.0.3

8269b00

Update tox from 3.14.0 to 3.14.3

3d1715a

Update coveralls from 1.8.2 to 1.10.0

7da4450

LuisAlejandro merged commit 35f98fb into develop Feb 2, 2020

LuisAlejandro deleted the pyup-scheduled-update-2020-02-01 branch February 2, 2020 15:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Scheduled monthly dependency update for February #48

Scheduled monthly dependency update for February #48

pyup-bot commented Feb 1, 2020

claassistantio commented Feb 1, 2020

Scheduled monthly dependency update for February #48

Scheduled monthly dependency update for February #48

Conversation

pyup-bot commented Feb 1, 2020

Update setuptools from 41.6.0 to 45.1.0.

45.1.0

45.0.0

44.0.0

43.0.0

42.0.2

42.0.1

42.0.0

Update pip from 19.3.1 to 20.0.2.

20.0.2

20.0.1

20.0

Update pydocstyle from 4.0.1 to 5.0.2.

Update virtualenv from 16.7.7 to 16.7.9.

16.7.9

16.7.8

Update coverage from 4.5.4 to 5.0.3.

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

Update tox from 3.14.0 to 3.14.3.

Update coveralls from 1.8.2 to 1.10.0.

1.10.0

1.9.2

1.9.1

1.9.0

claassistantio commented Feb 1, 2020