codecov[bot]
commented
4 years ago Codecov Report
Merging #34 into master will decrease coverage by
0.97%. The diff coverage isn/a.
@@ Coverage Diff @@
## master #34 +/- ##
==========================================
- Coverage 95.12% 94.14% -0.98%
==========================================
Files 3 3
Lines 205 205
==========================================
- Hits 195 193 -2
- Misses 10 12 +2 | Impacted Files | Coverage Δ | |
|---|---|---|
| fs/youtube/youtubefs.py | 92.89% <0.00%> (-1.19%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 08784d6...018bbff. Read the comment docs.
pyup-bot
Update setuptools from 41.2.0 to 50.3.0.
Changelog
### 50.3.0 ``` ------- * 2368: In distutils, restore support for monkeypatched CCompiler.spawn per pypa/distutils15. ``` ### 50.2.0 ``` ------- * 2355: When pip is imported as part of a build, leave distutils patched. * 2380: There are some setuptools specific changes in the `setuptools.command.bdist_rpm` module that are no longer needed, because they are part of the `bdist_rpm` module in distutils in Python 3.5.0. Therefore, code was removed from `setuptools.command.bdist_rpm`. ``` ### 50.1.0 ``` ------- * 2350: Setuptools reverts using the included distutils by default. Platform maintainers and system integrators and others are *strongly* encouraged to set ``SETUPTOOLS_USE_DISTUTILS=local`` to help identify and work through the reported issues with distutils adoption, mainly to file issues and pull requests with pypa/distutils such that distutils performs as needed across every supported environment. ``` ### 50.0.3 ``` ------- * 2363: Restore link_libpython support on Python 3.7 and earlier (see pypa/distutils9). ``` ### 50.0.2 ``` ------- * 2352: In distutils hack, use absolute import rather than relative to avoid bpo-30876. ``` ### 50.0.1 ``` ------- * 2357: Restored Python 3.5 support in distutils.util for missing `subprocess._optim_args_from_interpreter_flags`. * 2358: Restored AIX support on Python 3.8 and earlier. * 2361: Add Python 3.10 support to _distutils_hack. Get the 'Loader' abstract class from importlib.abc rather than importlib.util.abc (alias removed in Python 3.10). ``` ### 50.0.0 ``` ------- * 2232: Once again, Setuptools overrides the stdlib distutils on import. For environments or invocations where this behavior is undesirable, users are provided with a temporary escape hatch. If the environment variable ``SETUPTOOLS_USE_DISTUTILS`` is set to ``stdlib``, Setuptools will fall back to the legacy behavior. Use of this escape hatch is discouraged, but it is provided to ease the transition while proper fixes for edge cases can be addressed. * 2334: In MSVC module, refine text in error message. ``` ### 49.6.0 ``` ------- * 2129: In pkg_resources, no longer detect any pathname ending in .egg as a Python egg. Now the path must be an unpacked egg or a zip file. ``` ### 49.5.0 ``` ------- * 2306: When running as a PEP 517 backend, setuptools does not try to install ``setup_requires`` itself. They are reported as build requirements for the frontend to install. ``` ### 49.4.0 ``` ------- * 2310: Updated vendored packaging version to 20.4. ``` ### 49.3.2 ``` ------- * 2300: Improve the ``safe_version`` function documentation * 2297: Once again, in stubs prefer exec_module to the deprecated load_module. ``` ### 49.3.1 ``` ------- * 2316: Removed warning when ``distutils`` is imported before ``setuptools`` when ``distutils`` replacement is not enabled. ``` ### 49.3.0 ``` ------- * 2259: Setuptools now provides a .pth file (except for editable installs of setuptools) to the target environment to ensure that when enabled, the setuptools-provided distutils is preferred before setuptools has been imported (and even if setuptools is never imported). Honors the SETUPTOOLS_USE_DISTUTILS environment variable. ``` ### 49.2.1 ``` ------- * 2257: Fixed two flaws in distutils._msvccompiler.MSVCCompiler.spawn. ``` ### 49.2.0 ``` ------- * 2230: Now warn the user when setuptools is imported after distutils modules have been loaded (exempting PyPy for 3.6), directing the users of packages to import setuptools first. ``` ### 49.1.3 ``` ------- * 2212: (Distutils) Allow spawn to accept environment. Avoid monkey-patching global state. * 2249: Fix extension loading technique in stubs. ``` ### 49.1.2 ``` ------- * 2232: In preparation for re-enabling a local copy of distutils, Setuptools now honors an environment variable, SETUPTOOLS_USE_DISTUTILS. If set to 'stdlib' (current default), distutils will be used from the standard library. If set to 'local' (default in a imminent backward-incompatible release), the local copy of distutils will be used. ``` ### 49.1.1 ``` ------- * 2094: Removed pkg_resources.py2_warn module, which is no longer reachable. ``` ### 49.1.0 ``` ------- * 2228: Disabled distutils adoption for now while emergent issues are addressed. ``` ### 49.0.1 ``` ------- * 2228: Applied fix for pypa/distutils3, restoring expectation that spawn will raise a DistutilsExecError when attempting to execute a missing file. ``` ### 49.0.0 ``` ------- * 2165: Setuptools no longer installs a site.py file during easy_install or develop installs. As a result, .eggs on PYTHONPATH will no longer take precedence over other packages on sys.path. If this issue affects your production environment, please reach out to the maintainers at 2165. * 2137: Removed (private) pkg_resources.RequirementParseError, now replaced by packaging.requirements.InvalidRequirement. Kept the name for compatibility, but users should catch InvalidRequirement instead. * 2180: Update vendored packaging in pkg_resources to 19.2. * 2199: Fix exception causes all over the codebase by using ``raise new_exception from old_exception`` ``` ### 48.0.0 ``` ------- * 2143: Setuptools adopts distutils from the Python 3.9 standard library and no longer depends on distutils in the standard library. When importing ``setuptools`` or ``setuptools.distutils_patch``, Setuptools will expose its bundled version as a top-level ``distutils`` package (and unload any previously-imported top-level distutils package), retaining the expectation that ``distutils``' objects are actually Setuptools objects. To avoid getting any legacy behavior from the standard library, projects are advised to always "import setuptools" prior to importing anything from distutils. This behavior happens by default when using ``pip install`` or ``pep517.build``. Workflows that rely on ``setup.py (anything)`` will need to first ensure setuptools is imported. One way to achieve this behavior without modifying code is to invoke Python thus: ``python -c "import setuptools; exec(open('setup.py').read())" (anything)``. ``` ### 47.3.2 ``` ------- * 2071: Replaced references to the deprecated imp package with references to importlib ``` ### 47.3.1 ``` ------- * 1973: Removed ``pkg_resources.py31compat.makedirs`` in favor of the stdlib. Use ``os.makedirs()`` instead. * 2198: Restore ``__requires__`` directive in easy-install wrapper scripts. ``` ### 47.3.0 ``` ------- * 2197: Console script wrapper for editable installs now has a unified template and honors importlib_metadata if present for faster script execution on older Pythons. * 2195: Fix broken entry points generated by easy-install (pip editable installs). ``` ### 47.2.0 ``` ------- * 2194: Editable-installed entry points now load significantly faster on Python versions 3.8+. ``` ### 47.1.1 ``` ------- * 2156: Update mailing list pointer in developer docs ``` ### 47.1.0 ``` ------- * 2070: In wheel-to-egg conversion, use simple pkg_resources-style namespace declaration for packages that declare namespace_packages. ``` ### 47.0.0 ``` ------- * 2094: Setuptools now actively crashes under Python 2. Python 3.5 or later is required. Users of Python 2 should use ``setuptools<45``. * 1700: Document all supported keywords by migrating the ones from distutils. ``` ### 46.4.0 ``` ------- * 1753: ``attr:`` now extracts variables through rudimentary examination of the AST, thereby supporting modules with third-party imports. If examining the AST fails to find the variable, ``attr:`` falls back to the old behavior of importing the module. Works on Python 3 only. ``` ### 46.3.1 ``` ------- No significant changes. ``` ### 46.3.0 ``` ------- * 2089: Package index functionality no longer attempts to remove an md5 fragment from the index URL. This functionality, added for distribute 163 is no longer relevant. * 2041: Preserve file modes during pkg files copying, but clear read only flag for target afterwards. * 2105: Filter ``2to3`` deprecation warnings from ``TestDevelop.test_2to3_user_mode``. ``` ### 46.2.0 ``` ------- * 2040: Deprecated the ``bdist_wininst`` command. Binary packages should be built as wheels instead. * 2062: Change 'Mac OS X' to 'macOS' in code. * 2075: Stop recognizing files ending with ``.dist-info`` as distribution metadata. * 2086: Deprecate 'use_2to3' functionality. Packagers are encouraged to use single-source solutions or build tool chains to manage conversions outside of setuptools. * 1698: Added documentation for ``build_meta`` (a bare minimum, not completed). * 2082: Filter ``lib2to3`` ``PendingDeprecationWarning`` and ``DeprecationWarning`` in tests, because ``lib2to3`` is `deprecated in Python 3.9 <https://bugs.python.org/issue40360>`_. ``` ### 46.1.3 ``` ------- No significant changes. ``` ### 46.1.2 ``` ------- * 1458: Added template for reporting Python 2 incompatibilities. ``` ### 46.1.1 ``` ------- No significant changes. ``` ### 46.1.0 ``` ------- * 308: Allow version number normalization to be bypassed by wrapping in a 'setuptools.sic()' call. * 1424: Prevent keeping files mode for package_data build. It may break a build if user's package data has read only flag. * 1431: In ``easy_install.check_site_dir``, ensure the installation directory exists. * 1563: In ``pkg_resources`` prefer ``find_spec`` (PEP 451) to ``find_module``. ``` ### 46.0.0 ``` ------- * 65: Once again as in 3.0, removed the Features feature. * 1890: Fix vendored dependencies so importing ``setuptools.extern.some_module`` gives the same object as ``setuptools._vendor.some_module``. This makes Metadata picklable again. * 1899: Test suite now fails on warnings. * 2011: Fix broken link to distutils docs on package_data * 1991: Include pkg_resources test data in sdist, so tests can be executed from it. ``` ### 45.3.0 ``` ------- * 1557: Deprecated eggsecutable scripts and updated docs. * 1904: Update msvc.py to use CPython 3.8.0 mechanism to find msvc 14+ ``` ### 45.2.0 ``` ------- * 1905: Fixed defect in _imp, introduced in 41.6.0 when the 'tests' directory is not present. * 1941: Improve editable installs with PEP 518 build isolation: * The ``--user`` option is now always available. A warning is issued if the user site directory is not available. * The error shown when the install directory is not in ``PYTHONPATH`` has been turned into a warning. * 1981: Setuptools now declares its ``tests`` and ``docs`` dependencies in metadata (extras). * 1985: Add support for installing scripts in environments where bdist_wininst is missing (i.e. Python 3.9). * 1968: Add flake8-2020 to check for misuse of sys.version or sys.version_info. ``` ### 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 >=9 or pin to Setuptools <45 to maintain 2.7 support. * 1959: Fix for Python 4: replace unsafe six.PY3 with six.PY2 ``` ### 44.1.1 ``` ------- * 2158: Avoid loading working set during ``Distribution.finalize_options`` prior to invoking ``_install_setup_requires``, broken since v42.0.0. ``` ### 44.1.0 ``` ------- * 1704: Set sys.argv[0] in setup script run by build_meta.__legacy__ * 1959: Fix for Python 4: replace unsafe six.PY3 with six.PY2 * 1994: Fixed a bug in the "setuptools.finalize_distribution_options" hook that lead to ignoring the order attribute of entry points managed by this hook. ``` ### 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 'setuptools' 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'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 <https://pip.pypa.io/en/stable/>`_ 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 "upload" and "register" commands in favor of `twine <https://pypi.org/p/twine>`_. * 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 'm' 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 "setuptools.finalize_distribution_options", enabling plugins like `setuptools_scm <https://pypi.org/project/setuptools_scm>`_ to configure options on the distribution at finalization time. ``` ### 41.6.0 ``` ------- * 479: Replace usage of deprecated ``imp`` module with local re-implementation in ``setuptools._imp``. ``` ### 41.5.1 ``` ------- * 1891: Fix code for detecting Visual Studio's version on Windows under Python 2. ``` ### 41.5.0 ``` ------- * 1811: Improve Visual C++ 14.X support, mainly for Visual Studio 2017 and 2019. * 1814: Fix ``pkg_resources.Requirement`` hash/equality implementation: take PEP 508 direct URL into account. * 1824: Fix tests when running under ``python3.10``. * 1878: Formally deprecated the ``test`` command, with the recommendation that users migrate to ``tox``. * 1860: Update documentation to mention the egg format is not supported by pip and dependency links support was dropped starting with pip 19.0. * 1862: Drop ez_setup documentation: deprecated for some time (last updated in 2016), and still relying on easy_install (deprecated too). * 1868: Drop most documentation references to (deprecated) EasyInstall. * 1884: Added a trove classifier to document support for Python 3.8. * 1886: Added Python 3.8 release to the Travis test matrix. ``` ### 41.4.0 ``` ------- * 1847: In declarative config, now traps errors when invalid ``python_requires`` values are supplied. ``` ### 41.3.0 ``` ------- * 1690: When storing extras, rely on OrderedSet to retain order of extras as indicated by the packager, which will also be deterministic on Python 2.7 (with PYTHONHASHSEED unset) and Python 3.6+. * 1858: Fixed failing integration test triggered by 'long_description_content_type' in packaging. ```Links
- PyPI: https://pypi.org/project/setuptools - Changelog: https://pyup.io/changelogs/setuptools/ - Repo: https://github.com/pypa/setuptoolsUpdate docutils from 0.15.2 to 0.16.
Changelog
### 0.16 ``` ========================= .. Note:: Docutils 0.15.x is the last version supporting Python 2.6, 3.3 and 3.4. Docutils 0.16.x supports Python 2.7 and Python >= 3.5 natively, without the use of the ``2to3`` tool. * reStructuredText: - Keep `backslash escapes`__ in the document tree. This allows, e.g., escaping of author-separators in `bibliographic fields`__. __ http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.htmlescaping-mechanism __ docs/ref/rst/restructuredtext.htmlbibliographic-fields * LaTeX writer: - Informal titles of type "rubric" default to bold-italic and left aligned. - Deprecate ``\docutilsrole`` prefix for styling commands: use ``\DUrole`` instead. - Fix topic subtitle. - Add "latex writers" to the `config_section_dependencies`. - Ignore classes for `rubric` elements (class wrapper interferes with LaTeX formatting). * tools/buildhtml.py - New option "--html-writer" allows to select "html__" (default), "html4" or "html5". __ html: docs/user/html.htmlhtml * docutils/io.py - Remove the `handle_io_errors` option from io.FileInput/Output. * docutils/nodes.py - If `auto_id_prefix`_ ends with "%", this is replaced with the tag name. .. _auto_id_prefix: docs/user/config.htmlauto-id-prefix * Various bugfixes and improvements (see HISTORY_). ```Links
- PyPI: https://pypi.org/project/docutils - Changelog: https://pyup.io/changelogs/docutils/ - Homepage: http://docutils.sourceforge.net/Update Pygments from 2.4.2 to 2.7.1.
Changelog
### 2.7.1 ``` ------------- (released September 16, 2020) - Fixed a regression in the JSON lexer (1544) ``` ### 2.7.0 ``` ------------- (released September 12, 2020) - Added lexers: * Arrow (PR1481, PR1499) * BARE (PR1488) * Devicetree (PR1434) * F* (PR1409) * GDScript (PR1457) * Pointless (PR1494) * PromQL (PR1506) * PsySH (PR1438) * Singularity (PR1285) * TiddlyWiki5 (PR1390) * TNT (PR1414) * YANG (PR1408, PR1428) - Updated lexers: * APL (PR1503) * C++ (PR1350, which also fixes: 1222, 996, 906, 828, 1162, 1166, 1396) * Chapel (PR1423) * CMake (1491) * CSound (1509) * Cython (PR1507) * Dart (PR1449) * Fennel (PR1535) * Fortran (PR1442) * GAS (PR1530) * HTTP (PR1432, 1520, PR1521) * Inform 6 (PR1461) * Javascript (PR1533) * JSON (1065, PR1528) * Lean (PR1415) * Matlab (PR1399) * Markdown (1492, PR1495) * MySQL (975, 1063, 1453, PR1527) * NASM (PR1465) * Nim (PR1426) * PostgreSQL (PR1513) * PowerShell (PR1398, PR1497) * Protobuf (PR1505) * Robot (PR1480) * SQL (PR1402) * SystemVerilog (PR1436, PR1452, PR1454, PR1460, PR1462, PR1463, PR1464, PR1471, 1496, PR1504) * TeraTerm (PR1337) * XML (1502) - Added a new filter for math symbols (PR1406) - The Kconfig lexer will match Kconfig derivative names now (PR1458) - Improved HTML formatter output (PR1500) - ``.markdown`` is now recognized as an extension for Markdown files (PR1476) - Fixed line number colors for Solarized (PR1477, 1356) - Improvements to exception handling (PR1478) - Improvements to tests (PR1532, PR1533, PR1539) - Various code cleanups (PR1536, PR1537, PR1538) ``` ### 2.6.1 ``` ------------- (released March 8, 2020) - This release fixes a packaging issue. No functional changes. ``` ### 2.6 ``` ----------- (released March 8, 2020) - Running Pygments on Python 2.x is no longer supported. (The Python 2 lexer still exists.) - Added lexers: * Linux kernel logs (PR1310) * LLVM MIR (PR1361) * MiniScript (PR1397) * Mosel (PR1287, PR1326) * Parsing Expression Grammar (PR1336) * ReasonML (PR1386) * Ride (PR1319, PR1321) * Sieve (PR1257) * USD (PR1290) * WebIDL (PR1309) - Updated lexers: * Apache2 (PR1378) * Chapel (PR1357) * CSound (PR1383) * D (PR1375, PR1362) * Idris (PR1360) * Perl6/Raku lexer (PR1344) * Python3 (PR1382, PR1385) * Rust: Updated lexer to cover more builtins (mostly macros) and miscellaneous new syntax (PR1320) * SQL: Add temporal support keywords (PR1402) - The 256-color/true-color terminal formatters now support the italic attribute in styles (PR1288) - Support HTTP 2/3 header (PR1308) - Support missing reason in HTTP header (PR1322) - Boogie/Silver: support line continuations and triggers, move contract keywords to separate category (PR1299) - GAS: support C-style comments (PR1291) - Fix names in S lexer (PR1330, PR1333) - Fix numeric literals in Ada (PR1334) - Recognize ``.mjs`` files as Javascript (PR1392) - Recognize ``.eex`` files as Elixir (PR1387) - Fix ``re.MULTILINE`` usage (PR1388) - Recognize ``pipenv`` and ``poetry`` dependency & lock files (PR1376) - Improve font search on Windows (1247) - Remove unused script block (1401) ``` ### 2.5.2 ``` ------------- (released November 29, 2019) - Fix incompatibility with some setuptools versions (PR1316) - Fix lexing of ReST field lists (PR1279) - Fix lexing of Matlab keywords as field names (PR1282) - Recognize double-quoted strings in Matlab (PR1278) - Avoid slow backtracking in Vim lexer (PR1312) - Fix Scala highlighting of types (PR1315) - Highlight field lists more consistently in ReST (PR1279) - Fix highlighting Matlab keywords in field names (PR1282) - Recognize Matlab double quoted strings (PR1278) - Add some Terraform keywords - Update Modelica lexer to 3.4 - Update Crystal examples ``` ### 2.5.1 ``` ------------- (released November 26, 2019) - This release fixes a packaging issue. No functional changes. ``` ### 2.5.0 ``` ------------- (released November 26, 2019) - Added lexers: * Email (PR1246) * Erlang, Elixir shells (PR823, 1521) * Notmuch (PR1264) * `Scdoc <https://git.sr.ht/~sircmpwn/scdoc>`_ (PR1268) * `Solidity <https://solidity.readthedocs.io/>`_ (1214) * `Zeek <https://www.zeek.org>`_ (new name for Bro) (PR1269) * `Zig <https://ziglang.org/>`_ (PR820) - Updated lexers: * Apache2 Configuration (PR1251) * Bash sessions (1253) * CSound (PR1250) * Dart * Dockerfile * Emacs Lisp * Handlebars (PR773) * Java (1101, 987) * Logtalk (PR1261) * Matlab (PR1271) * Praat (PR1277) * Python3 (PR1255, PR1400) * Ruby * YAML (1528) * Velocity - Added styles: * Inkpot (PR1276) - The ``PythonLexer`` class is now an alias for the former ``Python3Lexer``. The old ``PythonLexer`` is available as ``Python2Lexer``. Same change has been done for the ``PythonTracebackLexer``. The ``python3`` option for the ``PythonConsoleLexer`` is now true by default. - Bump ``NasmLexer`` priority over ``TasmLexer`` for ``.asm`` files (fixes 1326) - Default font in the ``ImageFormatter`` has been updated (928, PR1245) - Test suite switched to py.test, removed nose dependency (1490) - Reduce ``TeraTerm`` lexer score -- it used to match nearly all languages (1256) - Treat ``Skylark``/``Starlark`` files as Python files (PR1259) - Image formatter: actually respect ``line_number_separator`` option - Add LICENSE file to wheel builds - Agda: fix lambda highlighting - Dart: support ` annotations - Dockerfile: accept ``FROM ... AS`` syntax - Emacs Lisp: add more string functions - GAS: accept registers in directive arguments - Java: make structural punctuation (braces, parens, colon, comma) ``Punctuation``, not ``Operator`` (987) - Java: support ``var`` contextual keyword (1101) - Matlab: Fix recognition of ``function`` keyword (PR1271) - Python: recognize ``.jy`` filenames (976) - Python: recognize ``f`` string prefix (1156) - Ruby: support squiggly heredocs - Shell sessions: recognize Virtualenv prompt (PR1266) - Velocity: support silent reference syntax ```Links
- PyPI: https://pypi.org/project/pygments - Changelog: https://pyup.io/changelogs/pygments/ - Homepage: https://pygments.org/Update codecov from 2.0.15 to 2.1.9.
Changelog
### 2.1.9 ``` - [289](https://github.com/codecov/codecov-python/pull/289)Remove token restriction as it is changed server-side ``` ### 2.1.8 ``` - [285](https://github.com/codecov/codecov-python/pull/285)Add support for CODECOV_FLAGS - [276](https://github.com/codecov/codecov-python/pull/276)Add ability to specify number of upload retries ``` ### 2.1.7 ``` - [279](https://github.com/codecov/codecov-python/pull/279) Fix pinned coverage version ``` ### 2.1.6 ``` - [275](https://github.com/codecov/codecov-python/pull/275) Fix GitHub Actions implementation ``` ### 2.1.5 ``` - [273](https://github.com/codecov/codecov-python/pull/273) Implement retries on Codecov API calls - [265](https://github.com/codecov/codecov-python/pull/265) Add GitHub Actions CI detection - [267](https://github.com/codecov/codecov-python/pull/267) Add CODECOV_NAME as default for name ``` ### 2.1.4 ``` - [260](https://github.com/codecov/codecov-python/pull/260) Enforce black formatting - [169](https://github.com/codecov/codecov-python/pull/169) Fix command line quoting on Windows - [216](https://github.com/codecov/codecov-python/pull/216) Fix GitLab CI project directory detection on Windows - [264](https://github.com/codecov/codecov-python/pull/264) Fix GitLab CI post version 9 - [262](https://github.com/codecov/codecov-python/pull/262) Check text for NoneType on writes - [266](https://github.com/codecov/codecov-python/pull/266) Include the cacert in the PUT call when uploading to S3 - [263](https://github.com/codecov/codecov-python/pull/263) Fixed gcov not being found in certain instances ``` ### 2.1.3 ``` - Fix find command not working on Windows - Add support for gzipping reports - Dynamic syncing of version ``` ### 2.1.1 ``` - Fix command when neither hg or git are not available ``` ### 2.1.0 ``` - Remove x-amz-acl header - Reformat with Black ``` ### 2.0.22 ``` - Cleaning TOC generation ``` ### 2.0.21 ``` - fixed string issues ``` ### 2.0.20 ``` - fixed broken subprocess handling ``` ### 2.0.19 ``` - fixed broken subprocess handling ``` ### 2.0.18 ``` - fixed broken subprocess handling ``` ### 2.0.17 ``` - fixed reported command injection vulnerability. ``` ### 2.0.16 ``` - fixed reported command injection vulnerability. ```Links
- PyPI: https://pypi.org/project/codecov - Changelog: https://pyup.io/changelogs/codecov/ - Repo: https://github.com/codecov/codecov-pythonUpdate green from 3.0.0 to 3.2.2.
Changelog
### 3.2.2 ``` 22 Sep 2020 - Fix help string for the `-O/--clear-omit` option. Resolves 231. - Tweak a bit of green's self-coverage to adjust for making releases in Python 3.8 r ``` ### 3.2.1 ``` 9 Aug 2020 - Fix passing tests not displaying captured stderr output unless stdout output was also present. Resolves 226. ``` ### 3.2.0 ``` 6 June 2020 - Fix crashes and hangs that could occur when using >1 subprocess due to a regression introduced in 3.1.1. - Add 'time' attributes to the `<testsuites>`, `<testsuite>`, and `<testcase>` fields in the Junit output for the `-j/--junit-report` output. Contributed by bkmd11 in 225. Resolves 208. ``` ### 3.1.4 ``` 7 May 2020 - Fix class/module teardowns being ignored. They are now reported as errors as they should be. Resolves 223. - Fix dates in this changelog--I was still using last year! 😆 ``` ### 3.1.3 ``` 5 May 2020 - Fix crash that could occur when whitespace is in the path on Windows. Contributed by bkmd11 in 222. ``` ### 3.1.2 ``` 4 May 2020 - Fix a crash that could occur during cleanup on unusual filesystems on Python 2. Note that Python 2 is still not supported...but might as well fix stuff if it is easy to fix. :-) Resolves 221. ``` ### 3.1.1 ``` 22 April 2020 - Fixed a hang that sometimes occurs in Python 3.8.0-3.8.2 due to a bug in upstream Python - Upstream bug report: https://bugs.python.org/issue39360 - Upstream fix in master: https://github.com/python/cpython/pull/19009 - Upstream fix in 3.8 branch (Maybe gets included in 3.8.3?): https://github.com/python/cpython/pull/19023 - Fixed behavior of raising SkipTest in a setUpClass class method on Python >= 3.8 ``` ### 3.1.0 ``` 3 Jan 2020 - You can now financially support Green by sponsoring CleanCut at https://github.com/sponsors/CleanCut - Added support for DocTests. I got interested in why charles-l's attempt to crash instead of hang when doctests were encountered didn't work, and ended up just adding support as a feature. To parse/run doctests for a particular module, in a _test_ module add `doctest_modules = [ ... ]` where each item is (preferably) an imported module or a dotted string representing a module to be imported that contains tests in docstrings. Resolves 88, 214. - Fixed a crash and a test failure that could occur with Coverage 5.x - Updated TravisCI builds with Python 3.8 on Linux and Xcode 11.3 on macOS. ```Links
- PyPI: https://pypi.org/project/green - Changelog: https://pyup.io/changelogs/green/ - Repo: https://github.com/CleanCut/green/tarball/3.2.2Update coverage from 4.5.4 to 5.3.
Changelog
### 5.3 ``` -------------------------- - The ``source`` setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new ``source_pkgs`` setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes `issue 268`_. - If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in `issue 1011`_. This is now fixed. .. _issue 268: https://github.com/nedbat/coveragepy/issues/268 .. _issue 1011: https://github.com/nedbat/coveragepy/issues/1011 .. _changes_521: ``` ### 5.2.1 ``` ---------------------------- - The dark mode HTML report still used light colors for the context listing, making them unreadable (`issue 1009`_). This is now fixed. - The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (`pull request 960`_). .. _pull request 960: https://github.com/nedbat/coveragepy/pull/960 .. _issue 1009: https://github.com/nedbat/coveragepy/issues/1009 .. _changes_52: ``` ### 5.2 ``` -------------------------- - The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (`issue 858`_ and `pull request 931`_). - The ``coverage report`` and ``coverage html`` commands now accept a ``--precision`` option to control the number of decimal points displayed. Thanks, Teake Nutma (`pull request 982`_). - The ``coverage report`` and ``coverage html`` commands now accept a ``--no-skip-covered`` option to negate ``--skip-covered``. Thanks, Anthony Sottile (`issue 779`_ and `pull request 932`_). - The ``--skip-empty`` option is now available for the XML report, closing `issue 976`_. - The ``coverage report`` command now accepts a ``--sort`` option to specify how to sort the results. Thanks, Jerin Peter George (`pull request 1005`_). - If coverage fails due to the coverage total not reaching the ``--fail-under`` value, it will now print a message making the condition clear. Thanks, Naveen Yadav (`pull request 977`_). - TOML configuration files with non-ASCII characters would cause errors on Windows (`issue 990`_). This is now fixed. - The output of ``--debug=trace`` now includes information about how the ``--source`` option is being interpreted, and the module names being considered. .. _pull request 931: https://github.com/nedbat/coveragepy/pull/931 .. _pull request 932: https://github.com/nedbat/coveragepy/pull/932 .. _pull request 977: https://github.com/nedbat/coveragepy/pull/977 .. _pull request 982: https://github.com/nedbat/coveragepy/pull/982 .. _pull request 1005: https://github.com/nedbat/coveragepy/pull/1005 .. _issue 779: https://github.com/nedbat/coveragepy/issues/779 .. _issue 858: https://github.com/nedbat/coveragepy/issues/858 .. _issue 976: https://github.com/nedbat/coveragepy/issues/976 .. _issue 990: https://github.com/nedbat/coveragepy/issues/990 .. _changes_51: ``` ### 5.1 ``` -------------------------- - The JSON report now includes counts of covered and missing branches. Thanks, Salvatore Zagaria. - On Python 3.8, try-finally-return reported wrong branch coverage with decorated async functions (`issue 964`_). This is now fixed. Thanks, Kjell Braden. - The :meth:`~coverage.Coverage.get_option` and :meth:`~coverage.Coverage.set_option` methods can now manipulate the ``[paths]`` configuration setting. Thanks to Bernát Gábor for the fix for `issue 967`_. .. _issue 964: https://github.com/nedbat/coveragepy/issues/964 .. _issue 967: https://github.com/nedbat/coveragepy/issues/967 .. _changes_504: ``` ### 5.0.4 ``` ---------------------------- - If using the ``[run] relative_files`` setting, the XML report will use relative files in the ``<source>`` 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't be sorted if localStorage wasn't available. This is now fixed: sorting works even though the sorting setting isn'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't work for test suites that changed directory before combining data, causing "Couldn't use data file: no such table: meta" errors (`issue 916`_). This is now fixed. - Coverage could fail to run your program with some form of "ModuleNotFound" or "ImportError" 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 "premain" debug option. - Added SQLite compile-time options to the "debug sys" 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 ("Already imported a file that will be measured") and a reduction in coverage totals (`issue 909`_). This is now fixed. - If no data was collected, an exception about "No data to report" 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 ("dynamic-conflict") 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 "file is not a database" error, then use a more specific error message, "Looks like a coverage 4.x data file, are you mixing versions of coverage?" Helps diagnose the problems described in `issue 886`_. - Measurement contexts and relative file names didn'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' 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 ".coverage". 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 <sleepy>`. .. _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 "pyproject.toml" 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 "reported" 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 "numbits." 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 "test_something" 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'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'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 "ctx" 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'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<.CoverageData.__init__>` 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'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 "missing" 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'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'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's default. This fixes `issue 715`_. - Improvements to context support: - The "no such table: meta" 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 "Who Tests What" (`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'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'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 "default value". - 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'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'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'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 .. _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://github.com/nedbat/coveragepy/issues/625 .. _issue 650: https://github.com/nedbat/coveragepy/issues/650 .. _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/coveragepyUpdate mock from 3.0.5 to 4.0.2.
Changelog
### 4.0.2 ``` ----- - Issue 39915: Ensure :attr:`unittest.mock.AsyncMock.await_args_list` has call objects in the order of awaited arguments instead of using :attr:`unittest.mock.Mock.call_args` which has the last value of the call. Patch by Karthikeyan Singaravelan. ``` ### 4.0.1 ``` ----- - Remove the universal marker from the wheel. ``` ### 4.0.0 ``` ----- - No Changes from 4.0.0b1. ``` ### 4.0.0b1 ``` ------- - The release is a fresh cut of cpython's `4a686504`__. All changes to :mod:`mock` from that commit and before are included in this release along with the subsequent changes listed below. __ https://github.com/python/cpython/commit/4a686504eb2bbf69adf78077458508a7ba131667 - Issue 37972: Subscripts to the `unittest.mock.call` objects now receive the same chaining mechanism as any other custom attributes, so that the following usage no longer raises a `TypeError`: call().foo().__getitem__('bar') Patch by blhsing - Issue 38839: Fix some unused functions in tests. Patch by Adam Johnson. - Issue 39485: Fix a bug in :func:`unittest.mock.create_autospec` that would complain about the wrong number of arguments for custom descriptors defined in an extension module returning functions. - Issue 39082: Allow AsyncMock to correctly patch static/class methods - Issue 38093: Fixes AsyncMock so it doesn't crash when used with AsyncContextManagers or AsyncIterators. - Issue 38859: AsyncMock now returns StopAsyncIteration on the exaustion of a side_effects iterable. Since PEP-479 its Impossible to raise a StopIteration exception from a coroutine. - Issue 38163: Child mocks will now detect their type as either synchronous or asynchronous, asynchronous child mocks will be AsyncMocks and synchronous child mocks will be either MagicMock or Mock (depending on their parent type). - Issue 38473: Use signature from inner mock for autospecced methods attached with :func:`unittest.mock.attach_mock`. Patch by Karthikeyan Singaravelan. - Issue 38136: Changes AsyncMock call count and await count to be two different counters. Now await count only counts when a coroutine has been awaited, not when it has been called, and vice-versa. Update the documentation around this. - Issue 37555: Fix `NonCallableMock._call_matcher` returning tuple instead of `_Call` object when `self._spec_signature` exists. Patch by Elizabeth Uselton - Issue 37251: Remove `__code__` check in AsyncMock that incorrectly evaluated function specs as async objects but failed to evaluate classes with `__await__` but no `__code__` attribute defined as async objects. - Issue 38669: Raise :exc:`TypeError` when passing target as a string with :meth:`unittest.mock.patch.object`. - Issue 25597: Ensure, if ``wraps`` is supplied to :class:`unittest.mock.MagicMock`, it is used to calculate return values for the magic methods instead of using the default return values. Patch by Karthikeyan Singaravelan. - Issue 38108: Any synchronous magic methods on an AsyncMock now return a MagicMock. Any asynchronous magic methods on a MagicMock now return an AsyncMock. - Issue 21478: Record calls to parent when autospecced object is attached to a mock using :func:`unittest.mock.attach_mock`. Patch by Karthikeyan Singaravelan. - Issue 38857: AsyncMock fix for return values that are awaitable types. This also covers side_effect iterable values that happend to be awaitable, and wraps callables that return an awaitable type. Before these awaitables were being awaited instead of being returned as is. - Issue 38932: Mock fully resets child objects on reset_mock(). Patch by Vegard Stikbakke - Issue 37685: Fixed ``__eq__``, ``__lt__`` etc implementations in some classes. They now return :data:`NotImplemented` for unsupported type of the other operand. This allows the other operand to play role (for example the equality comparison with :data:`~unittest.mock.ANY` will return ``True``). - Issue 37212: :func:`unittest.mock.call` now preserves the order of keyword arguments in repr output. Patch by Karthikeyan Singaravelan. - Issue 37828: Fix default mock name in :meth:`unittest.mock.Mock.assert_called` exceptions. Patch by Abraham Toriz Cruz. - Issue 36871: Improve error handling for the assert_has_calls and assert_has_awaits methods of mocks. Fixed a bug where any errors encountered while binding the expected calls to the mock's spec were silently swallowed, leading to misleading error output. - Issue 21600: Fix :func:`mock.patch.stopall` to stop active patches that were created with :func:`mock.patch.dict`. - Issue 38161: Removes _AwaitEvent from AsyncMock. - Issue 36871: Ensure method signature is used instead of constructor signature of a class while asserting mock object against method calls. Patch by Karthikeyan Singaravelan. ```Links
- PyPI: https://pypi.org/project/mock - Changelog: https://pyup.io/changelogs/mock/ - Docs: http://mock.readthedocs.org/en/latest/