Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Update pytest to 3.6.4 #230

Merged
merged 1 commit into from
Jul 30, 2018
Merged

Update pytest to 3.6.4 #230

merged 1 commit into from
Jul 30, 2018

Conversation

pyup-bot
Copy link
Collaborator

This PR updates pytest from 3.6.3 to 3.6.4.

Changelog

3.6.4

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

Bug Fixes
---------

- Invoke pytest using ``-mpytest`` so ``sys.path`` does not get polluted by packages installed in ``site-packages``. (`742 <https://github.com/pytest-dev/pytest/issues/742>`_)


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

- Use ``smtp_connection`` instead of ``smtp`` in fixtures documentation to avoid possible confusion. (`3592 <https://github.com/pytest-dev/pytest/issues/3592>`_)


Trivial/Internal Changes
------------------------

- Remove obsolete ``__future__`` imports. (`2319 <https://github.com/pytest-dev/pytest/issues/2319>`_)

- Add CITATION to provide information on how to formally cite pytest. (`3402 <https://github.com/pytest-dev/pytest/issues/3402>`_)

- Replace broken type annotations with type comments. (`3635 <https://github.com/pytest-dev/pytest/issues/3635>`_)

- Pin ``pluggy`` to ``<0.8``. (`3727 <https://github.com/pytest-dev/pytest/issues/3727>`_)
Links

@coveralls
Copy link

coveralls commented Jul 29, 2018

Coverage Status

Coverage remained the same at 70.257% when pulling 5a21e7f on pyup-update-pytest-3.6.3-to-3.6.4 into b7fb58e on master.

@nicfit nicfit merged commit 3fdb334 into master Jul 30, 2018
@nicfit nicfit deleted the pyup-update-pytest-3.6.3-to-3.6.4 branch July 30, 2018 15:50
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.

None yet

3 participants