Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Scheduled weekly dependency update for week 27 #7489

Closed
wants to merge 2 commits into from

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Jul 6, 2020

Update coverage from 5.1 to 5.2.

Changelog

5.2

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

- The HTML report has been redesigned by Victor 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:
Links

Update isort from 4.3.21 to 5.0.4.

Changelog

5.0.4

- Fixed 1264: a regression with comment handling and `force_sort_within_sections` config option
- Added warning for deprecated CLI flags and linked to upgrade guide.

5.0.3

- Fixed setup.py command incorrectly passing check=True as a configuration parameter (see: https://github.com/timothycrosley/isort/issues/1258)
- Fixed missing patch version
- Fixed issue 1253: Atomic fails when passed in not readable output stream

5.0.2

- Ensured black profile was complete, adding missing line_length definition.

5.0.1

- Fixed a runtime error in a vendored dependency (toml).

5.0.0

**Breaking changes:**

- isort now requires Python 3.6+ to run but continues to support formatting on ALL versions of python including
 Python 2 code.
- isort deprecates official support for Python 3.4, removing modules only in this release from known_standard_library:
   - user
- Config files are no longer composed on-top of each-other. Instead the first config file found is used.
 - Since there is no longer composition negative form settings (such as --dont-skip or it's config file variant `not_skip`) are no longer required and have been removed.
- Two-letter shortened setting names (like `ac` for `atomic`) now require two dashes to avoid ambiguity: `--ac`.
- For consistency with other tools `-v` now is shorthand for verbose and `-V` is shorthand for version. See Issue: 1067.
- `length_sort_{section_name}` config usage has been deprecated. Instead `length_sort_sections` list can be used to specify a list of sections that need to be length sorted.
- `safety_excludes` and `unsafe` have been deprecated
- Config now includes as default full set of safety directories defined by safety excludes.
- `--recursive` option has been removed. Directories passed in are now automatically sorted recursive.
- `--apply` option has been removed as it is the default behaviour.
- isort now does nothing, beyond giving instructions and exiting status code 0, when ran with no arguments.
 - a new `--interactive` flag has been added to enable the old style behaviour.
- isort now works on contiguous sections of imports, instead of one whole file at a time.
- isort now formats all nested "as" imports in the "from" form. `import x.y as a` becomes `from x import y as a`.
- `keep_direct_and_as_imports` option now defaults to `True`.
- `appdirs` is no longer supported. Unless manually specified, config should be project config only.
- `toml` is now installed as a vendorized module, meaning pyproject.toml based config is always supported.
- Completely new Python API, old version is removed and no longer accessible.
- New module placement logic and module fully replaces old finders. Old approach is still available via `--old-finders`.

Internal:

- isort now utilizes mypy and typing to filter out typing related issues before deployment.
- isort now utilizes black internally to ensure more consistent formatting.

- profile support for common project types (black, django, google, etc)

- Much much more. There is some difficulty in fully capturing the extent of changes in this release - just because of how all encompassing the release is. See: [Github Issues](https://github.com/timothycrosley/isort/issues?q=is%3Aissue+is%3Aclosed) for more.
Links

@vorpal-buildbot
Copy link
Contributor

Changelogs

coverage 5.2


  • The HTML report has been redesigned by Victor 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: nedbat/coveragepy#931
.. _pull request 932: nedbat/coveragepy#932
.. _pull request 977: nedbat/coveragepy#977
.. _pull request 982: nedbat/coveragepy#982
.. _pull request 1005: nedbat/coveragepy#1005
.. _issue 779: nedbat/coveragepy#779
.. _issue 858: nedbat/coveragepy#858
.. _issue 976: nedbat/coveragepy#976
.. _issue 990: nedbat/coveragepy#990

.. _changes_51:

isort 5.0.4

  • Fixed 1264: a regression with comment handling and force_sort_within_sections config option
  • Added warning for deprecated CLI flags and linked to upgrade guide.

isort 5.0.3

isort 5.0.2

  • Ensured black profile was complete, adding missing line_length definition.

isort 5.0.1

  • Fixed a runtime error in a vendored dependency (toml).

isort 5.0.0

Breaking changes:

  • isort now requires Python 3.6+ to run but continues to support formatting on ALL versions of python including
    Python 2 code.
  • isort deprecates official support for Python 3.4, removing modules only in this release from known_standard_library:
    • user
  • Config files are no longer composed on-top of each-other. Instead the first config file found is used.
    • Since there is no longer composition negative form settings (such as --dont-skip or it's config file variant not_skip) are no longer required and have been removed.
  • Two-letter shortened setting names (like ac for atomic) now require two dashes to avoid ambiguity: --ac.
  • For consistency with other tools -v now is shorthand for verbose and -V is shorthand for version. See Issue: 1067.
  • length_sort_{section_name} config usage has been deprecated. Instead length_sort_sections list can be used to specify a list of sections that need to be length sorted.
  • safety_excludes and unsafe have been deprecated
  • Config now includes as default full set of safety directories defined by safety excludes.
  • --recursive option has been removed. Directories passed in are now automatically sorted recursive.
  • --apply option has been removed as it is the default behaviour.
  • isort now does nothing, beyond giving instructions and exiting status code 0, when ran with no arguments.
    • a new --interactive flag has been added to enable the old style behaviour.
  • isort now works on contiguous sections of imports, instead of one whole file at a time.
  • isort now formats all nested "as" imports in the "from" form. import x.y as a becomes from x import y as a.
  • keep_direct_and_as_imports option now defaults to True.
  • appdirs is no longer supported. Unless manually specified, config should be project config only.
  • toml is now installed as a vendorized module, meaning pyproject.toml based config is always supported.
  • Completely new Python API, old version is removed and no longer accessible.
  • New module placement logic and module fully replaces old finders. Old approach is still available via --old-finders.

Internal:

  • isort now utilizes mypy and typing to filter out typing related issues before deployment.

  • isort now utilizes black internally to ensure more consistent formatting.

  • profile support for common project types (black, django, google, etc)

  • Much much more. There is some difficulty in fully capturing the extent of changes in this release - just because of how all encompassing the release is. See: Github Issues for more.

@codecov
Copy link

codecov bot commented Jul 6, 2020

Codecov Report

Merging #7489 into master will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7489      +/-   ##
==========================================
- Coverage   45.51%   45.51%   -0.01%     
==========================================
  Files         279      279              
  Lines       14060    14060              
  Branches     2122     2122              
==========================================
- Hits         6400     6399       -1     
  Misses       7368     7368              
- Partials      292      293       +1     
Impacted Files Coverage Δ
magic/image_fetcher.py 34.61% <0.00%> (-1.29%) ⬇️
decksite/league.py 34.32% <0.00%> (-0.34%) ⬇️
discordbot/commands/tournament.py 85.71% <0.00%> (ø)
decksite/data/competition.py 65.43% <0.00%> (+2.46%) ⬆️

Continue to review full report at Codecov.

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

@pyup-bot
Copy link
Contributor Author

Closing this in favor of #7513

@pyup-bot pyup-bot closed this Jul 13, 2020
@silasary silasary deleted the pyup-scheduled-update-2020-07-06 branch July 13, 2020 18:38
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants