search

hasgeek / lastuser

Lastuser has been merged into Funnel. This repository is archived.
https://hasgeek.com/
BSD 2-Clause "Simplified" License
166 stars 30 forks source link

Scheduled monthly dependency update for February #376

Closed pyup-bot closed 4 years ago

pyup-bot commented 4 years ago

Update flake8-builtins from 1.4.1 to 1.4.2.

Changelog ### 1.4.2 ``` ------------------ - Fix tuple parsing. [memery-imb] ```
Links - PyPI: https://pypi.org/project/flake8-builtins - Changelog: https://pyup.io/changelogs/flake8-builtins/ - Repo: https://github.com/gforcada/flake8-builtins

Update flake8-comprehensions from 3.0.1 to 3.2.2.

Changelog ### 3.2.2 ``` ------------------ * Remove check for dict comprehensions in rule C407 as it would also change the results for certain builtins such as ``sum()``. ``` ### 3.2.1 ``` ------------------ * Remove check for set comprehensions in rule C407 as it would change the results for certain builtins such as ``sum()``. ``` ### 3.2.0 ``` ------------------ * Add ``filter`` and ``map`` to rule C407. * Check for dict and set comprehensions in rules C407 and C412. ``` ### 3.1.4 ``` ------------------ * Remove the tuple/unpacking check from C416 to prevent false positives where the type of the iterable is changed from some iterable to a tuple. ``` ### 3.1.3 ``` ------------------ * Ensure the fix for false positives in ``C416`` rule for asynchronous comprehensions runs on Python 3.6 too. ``` ### 3.1.2 ``` ------------------ * Fix false positives in ``C416`` rule for list comprehensions returning tuples. ``` ### 3.1.1 ``` ------------------ * Fix false positives in ``C416`` rule for asynchronous comprehensions. ``` ### 3.1.0 ``` ------------------ * Update Python support to 3.5-3.8. * Fix false positives for C404 for list comprehensions not directly creating tuples. * Add ``C413`` rule that checks for unnecessary use of ``list()`` or ``reversed()`` around ``sorted()``. * Add ``C414`` rule that checks for unnecessary use of the following: * ``list()``, ``reversed()``, ``sorted()``, or ``tuple()`` within ``set`` or ``sorted()`` * ``list()`` or ``tuple()`` within ``list()`` or ``tuple()`` * ``set()`` within ``set`` * Add ``C415`` rule that checks for unnecessary reversal of an iterable via subscript within ``reversed()``, ``set()``, or ``sorted()``. * Add ``C416`` rule that checks for unnecessary list or set comprehensions that can be rewritten using ``list()`` or ``set()``. ```
Links - PyPI: https://pypi.org/project/flake8-comprehensions - Changelog: https://pyup.io/changelogs/flake8-comprehensions/ - Repo: https://github.com/adamchainz/flake8-comprehensions

Update flake8-isort from 2.7.0 to 2.8.0.

Changelog ### 2.8.0 ``` ------------------ - Look for isort configuration on `.flake8` files as well. [JohnHBrock] - Document how to install `flake8-isort` on conda. [marcelotrevisani] - Look for isort configuration on `pyproject.toml` files as well. [sanjioh] ```
Links - PyPI: https://pypi.org/project/flake8-isort - Changelog: https://pyup.io/changelogs/flake8-isort/ - Repo: https://github.com/gforcada/flake8-isort

Update flake8-print from 3.1.3 to 3.1.4.

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

Links - PyPI: https://pypi.org/project/flake8-print - Changelog: https://pyup.io/changelogs/flake8-print/ - Repo: https://github.com/jbkahn/flake8-print

Update pep8-naming from 0.8.2 to 0.9.1.

Changelog ### 0.9.1 ``` ------------------ * Fix line number offsets when reporting errors involving functions with decorators in Python 3.8 and later. ``` ### 0.9.0 ``` ------------------ * Drop support for Python 3.3 and 3.4. * Support positional-only arguments in Python 3.8. * Recognize ``abc.ABCMeta`` as a metaclass base type. * ``ignore-names`` now also applies to the N803 check. * Handle assigning exceptions to object attributes in Python 2. ```
Links - PyPI: https://pypi.org/project/pep8-naming - Changelog: https://pyup.io/changelogs/pep8-naming/ - Repo: https://github.com/PyCQA/pep8-naming

Update pre-commit from 1.20.0 to 2.0.1.

Changelog ### 2.0.1 ``` ================== Fixes - Fix `ImportError` in python 3.6.0 / 3.6.1 for `typing.NoReturn` - 1302 PR by asottile. ``` ### 2.0.0 ``` ================== Features - Expose `PRE_COMMIT_REMOTE_NAME` and `PRE_COMMIT_REMOTE_URL` as environment variables during `pre-push` hooks. - 1274 issue by dmbarreiro. - 1288 PR by dmbarreiro. Fixes - Fix `python -m pre_commit --version` to mention `pre-commit` instead of `__main__.py`. - 1273 issue by ssbarnea. - 1276 PR by orcutt989. - Don't filter `GIT_SSL_NO_VERIFY` from environment when cloning. - 1293 PR by schiermike. - Allow `pre-commit init-templatedir` to succeed even if `core.hooksPath` is set. - 1298 issue by damienrj. - 1299 PR by asottile. Misc - Fix changelog date for 1.21.0. - 1275 PR by flaudisio. Updating - Removed `pcre` language, use `pygrep` instead. - 1268 PR by asottile. - Removed `--tags-only` argument to `pre-commit autoupdate` (it has done nothing since 0.14.0). - 1269 by asottile. - Remove python2 / python3.5 support. Note that pre-commit still supports running hooks written in python2, but pre-commit itself requires python 3.6+. - 1260 issue by asottile. - 1277 PR by asottile. - 1281 PR by asottile. - 1282 PR by asottile. - 1287 PR by asottile. - 1289 PR by asottile. - 1292 PR by asottile. ``` ### 1.21.0 ``` =================== Features - Add `conda` as a new `language`. - 1204 issue by xhochy. - 1232 PR by xhochy. - Add top-level configuration `files` for file selection. - 1220 issue by TheButlah. - 1248 PR by asottile. - Rework `--verbose` / `verbose` to be more consistent with normal runs. - 1249 PR by asottile. - Add support for the `pre-merge-commit` git hook. - 1210 PR by asottile. - this requires git 2.24+. - Add `pre-commit autoupdate --freeze` which produces "frozen" revisions. - 1068 issue by SkypLabs. - 1256 PR by asottile. - Display hook runtime duration when run with `--verbose`. - 1144 issue by potiuk. - 1257 PR by asottile. Fixes - Produce better error message when erroneously running inside of `.git`. - 1219 issue by Nusserdt. - 1224 PR by asottile. - Note: `git` has since fixed this bug: git/git36fd304d - Produce better error message when hook installation fails. - 1250 issue by asottile. - 1251 PR by asottile. - Fix cloning when `GIT_SSL_CAINFO` is necessary. - 1253 issue by igankevich. - 1254 PR by igankevich. - Fix `pre-commit try-repo` for bare, on-disk repositories. - 1258 issue by webknjaz. - 1259 PR by asottile. - Add some whitespace to `pre-commit autoupdate` to improve terminal autolink. - 1261 issue by yhoiseth. - 1262 PR by yhoiseth. Misc. - Minor code documentation updates. - 1200 PR by ryanrhee. - 1201 PR by ryanrhee. ```
Links - PyPI: https://pypi.org/project/pre-commit - Changelog: https://pyup.io/changelogs/pre-commit/ - Repo: https://github.com/pre-commit/pre-commit

Update Flask-Assets from 0.12 to 2.0.

Changelog ### 2.0 ``` - Compatibility with webassets 2.0. ```
Links - PyPI: https://pypi.org/project/flask-assets - Changelog: https://pyup.io/changelogs/flask-assets/ - Repo: http://github.com/miracle2k/flask-assets

Update sqlalchemy_utils from 0.34.2 to 0.36.1.

Changelog ### 0.36.1 ``` ^^^^^^^^^^^^^^^^^^^ - Added support for CASCADE option when dropping views (406, pull request courtesy of amicks) - Added `aliases` parameter to create_materialized_view function. ``` ### 0.36.0 ``` ^^^^^^^^^^^^^^^^^^^ - Removed explain and explain_analyze due to the internal changes in SQLAlchemy version 1.3. ``` ### 0.35.0 ``` ^^^^^^^^^^^^^^^^^^^ - Removed some deprecation warnings - Added Int8RangeType (401, pull request courtesy of lpsinger) ```
Links - PyPI: https://pypi.org/project/sqlalchemy-utils - Changelog: https://pyup.io/changelogs/sqlalchemy-utils/ - Repo: https://github.com/kvesteri/sqlalchemy-utils

Update phonenumbers from 8.10.22 to 8.11.2.

Changelog ### 8.11.0 ``` --------------------- Merge to [upstream commit ca195d5aff67](https://github.com/google/libphonenumber/commit/ca195d5aff67); just metadata changes. ```
Links - PyPI: https://pypi.org/project/phonenumbers - Changelog: https://pyup.io/changelogs/phonenumbers/ - Repo: https://github.com/daviddrysdale/python-phonenumbers

Update coverage from 4.5.4 to 5.0.3.

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

Changelog ### 1.10.0 ``` Features * support coverage>=5.0 (214) ([4a917402](4a917402)) <a name="1.9.2"></a> ``` ### 1.9.2 ``` Bug Fixes * **github:** fixup incorrect API usage (209) ([c338cab4](c338cab4)) <a name="1.9.1"></a> ``` ### 1.9.1 ``` Compatibility * this release marks Python 3.8 as officially supported. Earlier versions probably supported Python 3.8 too, but now we're *sure*. <a name="1.9.0"></a> ``` ### 1.9.0 ``` Features * **support:** support Github Actions CI (207) ([817119c3](817119c3)) Bug Fixes * **compatibility:** fixup coverage.__version__ comparisons (208) ([03a57a9a](03a57a9a)) <a name="1.8.2"></a> ```
Links - PyPI: https://pypi.org/project/coveralls - Changelog: https://pyup.io/changelogs/coveralls/ - Repo: http://github.com/coveralls-clients/coveralls-python