Skip to content

Update pytest-mypy to 0.4.0#73

Closed
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-pytest-mypy-0.3.2-to-0.4.0
Closed

Update pytest-mypy to 0.4.0#73
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-pytest-mypy-0.3.2-to-0.4.0

Conversation

@pyup-bot
Copy link
Copy Markdown
Collaborator

This PR updates pytest-mypy from 0.3.2 to 0.4.0.

Changelog

0.4.0

* Run mypy once per session instead of once per file.
* Stop passing --incremental (which mypy now defaults to).
* Support configuring the plugin in a conftest.py.
* Add support for Python 3.8

See [the milestone](https://github.com/dbader/pytest-mypy/milestone/6) for details.

0.3.3

* Register `mypy` marker.
* Add a PEP-518 [build-system]
* Add dependency pins for Python 3.4.
* Add support for Python 3.7

See [the milestone](https://github.com/dbader/pytest-mypy/milestone/3) for details.
Links

@codecov-io
Copy link
Copy Markdown

codecov-io commented Aug 24, 2019

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master    #73   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines           9      9           
=====================================
  Hits            9      9

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 4688bec...ca594c0. Read the comment docs.

@pyup-bot
Copy link
Copy Markdown
Collaborator Author

Closing this in favor of #75

@pyup-bot pyup-bot closed this Sep 19, 2019
@hellysmile hellysmile deleted the pyup-update-pytest-mypy-0.3.2-to-0.4.0 branch September 19, 2019 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants