Scheduled monthly dependency update for March

[pyup-bot]

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

coverage	4.4.1	»	4.5.1	PyPI | Changelog | Repo
flake8	3.4.1	»	3.5.0	PyPI | Changelog | Repo
isort	4.2.15	»	4.3.4	PyPI | Changelog | Repo
pytest	3.2.2	»	3.4.1	PyPI | Changelog | Repo | Homepage
pytest-mock	1.6.3	»	1.7.1	PyPI | Changelog | Repo
pytest-sugar	0.9.0	»	0.9.1	PyPI | Changelog | Homepage

Changelogs

coverage 4.4.1 -> 4.5.1

4.5.1

---

• Now that 4.5 properly separated the [run] omit and [report] omit
  settings, an old bug has become apparent. If you specified a package name
  for [run] source, then omit patterns weren't matched inside that package.
  This bug (issue 638_) is now fixed.

• On Python 3.7, reporting about a decorated function with no body other than a
  docstring would crash coverage.py with an IndexError (issue 640_). This is
  now fixed.

• Configurer plugins are now reported in the output of --debug=sys.

.. _issue 638: https://bitbucket.org/ned/coveragepy/issues/638/run-omit-is-ignored-since-45
.. _issue 640: https://bitbucket.org/ned/coveragepy/issues/640/indexerror-reporting-on-an-empty-decorated

.. _changes_45:

4.5

---

• A new kind of plugin is supported: configurators are invoked at start-up to
  allow more complex configuration than the .coveragerc file can easily do.
  See :ref:api_plugin for details. This solves the complex configuration
  problem described in issue 563_.

• The fail_under option can now be a float. Note that you must specify the
  [report] precision configuration option for the fractional part to be
  used. Thanks to Lars Hupfeldt Nielsen for help with the implementation.
  Fixes issue 631_.

• The include and omit options can be specified for both the [run]
  and [report] phases of execution. 4.4.2 introduced some incorrect
  interactions between those phases, where the options for one were confused
  for the other. This is now corrected, fixing issue 621_ and issue 622_.
  Thanks to Daniel Hahler for seeing more clearly than I could.

• The coverage combine command used to always overwrite the data file, even
  when no data had been read from apparently combinable files. Now, an error
  is raised if we thought there were files to combine, but in fact none of them
  could be used. Fixes issue 629_.

• The coverage combine command could get confused about path separators
  when combining data collected on Windows with data collected on Linux, as
  described in issue 618_. This is now fixed: the result path always uses
  the path separator specified in the [paths] result.

• On Windows, the HTML report could fail when source trees are deeply nested,
  due to attempting to create HTML filenames longer than the 250-character
  maximum. Now filenames will never get much larger than 200 characters,
  fixing issue 627_. Thanks to Alex Sandro for helping with the fix.

.. _issue 563: https://bitbucket.org/ned/coveragepy/issues/563/platform-specific-configuration
.. _issue 618: https://bitbucket.org/ned/coveragepy/issues/618/problem-when-combining-windows-generated
.. _issue 621: https://bitbucket.org/ned/coveragepy/issues/621/include-ignored-warning-when-using
.. _issue 622: https://bitbucket.org/ned/coveragepy/issues/622/report-omit-overwrites-run-omit
.. _issue 627: https://bitbucket.org/ned/coveragepy/issues/627/failure-generating-html-reports-when-the
.. _issue 629: https://bitbucket.org/ned/coveragepy/issues/629/multiple-use-of-combine-leads-to-empty
.. _issue 631: https://bitbucket.org/ned/coveragepy/issues/631/precise-coverage-percentage-value

.. _changes_442:

4.4.2

---

• Support for Python 3.7. In some cases, class and module docstrings are no
  longer counted in statement totals, which could slightly change your total
  results.

• Specifying both --source and --include no longer silently ignores the
  include setting, instead it displays a warning. Thanks, Loïc Dachary. Closes
  issue 265_ and issue 101_.

• Fixed a race condition when saving data and multiple threads are tracing
  (issue 581_). It could produce a "dictionary changed size during iteration"
  RuntimeError. I believe this mostly but not entirely fixes the race
  condition. A true fix would likely be too expensive. Thanks, Peter Baughman
  for the debugging, and Olivier Grisel for the fix with tests.

• Configuration values which are file paths will now apply tilde-expansion,
  closing issue 589_.

• Now secondary config files like tox.ini and setup.cfg can be specified
  explicitly, and prefixed sections like [coverage:run] will be read. Fixes
  issue 588_.

• Be more flexible about the command name displayed by help, fixing
  issue 600_. Thanks, Ben Finney.

.. _issue 101: https://bitbucket.org/ned/coveragepy/issues/101/settings-under-report-affect-running
.. _issue 581: https://bitbucket.org/ned/coveragepy/issues/581/race-condition-when-saving-data-under
.. _issue 588: https://bitbucket.org/ned/coveragepy/issues/588/using-rcfile-path-to-toxini-uses-run
.. _issue 589: https://bitbucket.org/ned/coveragepy/issues/589/allow-expansion-in-coveragerc
.. _issue 600: https://bitbucket.org/ned/coveragepy/issues/600/get-program-name-from-command-line-when

.. _changes_441:

flake8 3.4.1 -> 3.5.0

3.5.0

---

You can view the 3.5.0 milestone_ on GitLab for more details.

New Dependency Information

• Allow for PyFlakes 1.6.0 (See also GitLab359_)

• Start using new PyCodestyle checks for bare excepts and ambiguous identifier
  (See also GitLab361_)

Features

• Print out information about configuring VCS hooks (See also GitLab335_)

• Allow users to develop plugins "local" to a repository without using
  setuptools. See our documentation on local plugins for more information.
  (See also GitLab357_)

Bugs Fixed

• Catch and helpfully report UnicodeDecodeError\ s when parsing
  configuration files. (See also GitLab358_)

.. all links
.. _3.5.0 milestone:
https://gitlab.com/pycqa/flake8/milestones/20

.. issue links
.. _GitLab335:
https://gitlab.com/pycqa/flake8/issues/335
.. _GitLab357:
https://gitlab.com/pycqa/flake8/issues/357
.. _GitLab358:
https://gitlab.com/pycqa/flake8/issues/358
.. _GitLab359:
https://gitlab.com/pycqa/flake8/issues/359
.. _GitLab361:
https://gitlab.com/pycqa/flake8/issues/361

.. merge request links

isort 4.2.15 -> 4.3.4

4.3.4

• Fixed issue 671: isort is corrupting CRLF files

4.3.3

• Fixed issue 665: Tabs turned into single spaces

4.3.2

• Fixed issue 651: Add imports option is broken
• Fixed issue 662: An error generated by rewriting .imports to . imoprts

4.3.1

• Fixed setup.py errors
• Fixed issue 654: Trailing comma count error
• Fixed issue 650: Wrong error message displayed

4.3.0

• Fixed 557: force_alphabetical_sort and force_sort_within_sections can now be utilized together without extra new lines
• Fix case-sensitive path existence check in Mac OS X
• Added --no-lines-before for more granular control over section output
• Fixed 493: Unwanted conversion to Windows line endings
• Fixed 590: Import as mucks with alphabetical sorting
• Implemented --version-number to retrieve just the version number without the isort logo
• Breaking changes
  • Python 2.7+ only (dropped 2.6) allowing various code simplifications and improvements.

pytest 3.2.2 -> 3.4.1

3.4.1

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

Bug Fixes

• Move import of doctest.UnexpectedException to top-level to avoid possible
  errors when using --pdb. (1810 <https://github.com/pytest-dev/pytest/issues/1810>_)

• Added printing of captured stdout/stderr before entering pdb, and improved a
  test which was giving false negatives about output capturing. (3052 <https://github.com/pytest-dev/pytest/issues/3052>_)

• Fix ordering of tests using parametrized fixtures which can lead to fixtures
  being created more than necessary. (3161 <https://github.com/pytest-dev/pytest/issues/3161>_)

• Fix bug where logging happening at hooks outside of "test run" hooks would
  cause an internal error. (3184 <https://github.com/pytest-dev/pytest/issues/3184>_)

• Detect arguments injected by unittest.mock.patch decorator correctly when
  pypi mock.patch is installed and imported. (3206 <https://github.com/pytest-dev/pytest/issues/3206>_)

• Errors shown when a pytest.raises() with match= fails are now cleaner
  on what happened: When no exception was raised, the "matching '...'" part got
  removed as it falsely implies that an exception was raised but it didn't
  match. When a wrong exception was raised, it's now thrown (like
  pytest.raised() without match= would) instead of complaining about
  the unmatched text. (3222 <https://github.com/pytest-dev/pytest/issues/3222>_)

• Fixed output capture handling in doctests on macOS. (985 <https://github.com/pytest-dev/pytest/issues/985>_)

Improved Documentation

• Add Sphinx parameter docs for match and message args to
  pytest.raises. (3202 <https://github.com/pytest-dev/pytest/issues/3202>_)

Trivial/Internal Changes

• pytest has changed the publication procedure and is now being published to
  PyPI directly from Travis. (3060 <https://github.com/pytest-dev/pytest/issues/3060>_)

• Rename ParameterSet._for_parameterize() to _for_parametrize() in
  order to comply with the naming convention. (3166 <https://github.com/pytest-dev/pytest/issues/3166>_)

• Skip failing pdb/doctest test on mac. (985 <https://github.com/pytest-dev/pytest/issues/985>_)

3.4.0

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

Deprecations and Removals

• All pytest classes now subclass object for better Python 2/3 compatibility.
  This should not affect user code except in very rare edge cases. (2147 <https://github.com/pytest-dev/pytest/issues/2147>_)

Features

• Introduce empty_parameter_set_mark ini option to select which mark to
  apply when pytest.mark.parametrize is given an empty set of parameters.
  Valid options are skip (default) and xfail. Note that it is planned
  to change the default to xfail in future releases as this is considered
  less error prone. (2527 <https://github.com/pytest-dev/pytest/issues/2527>_)

• Incompatible change: after community feedback the logging <https://docs.pytest.org/en/latest/logging.html>_ functionality has
  undergone some changes. Please consult the logging documentation <https://docs.pytest.org/en/latest/logging.htmlincompatible-changes-in-pytest-3-4>_
  for details. (3013 <https://github.com/pytest-dev/pytest/issues/3013>_)

• Console output falls back to "classic" mode when capturing is disabled (-s),
  otherwise the output gets garbled to the point of being useless. (3038 <https://github.com/pytest-dev/pytest/issues/3038>_)

• New pytest_runtest_logfinish <https://docs.pytest.org/en/latest/writing_plugins.html_pytest.hookspec.pytest_runtest_logfinish>_
  hook which is called when a test item has finished executing, analogous to
  pytest_runtest_logstart <https://docs.pytest.org/en/latest/writing_plugins.html_pytest.hookspec.pytest_runtest_start>.
  (3101 <https://github.com/pytest-dev/pytest/issues/3101>)

• Improve performance when collecting tests using many fixtures. (3107 <https://github.com/pytest-dev/pytest/issues/3107>_)

• New caplog.get_records(when) method which provides access to the captured
  records for the "setup", "call" and "teardown"
  testing stages. (3117 <https://github.com/pytest-dev/pytest/issues/3117>_)

• New fixture record_xml_attribute that allows modifying and inserting
  attributes on the <testcase> xml node in JUnit reports. (3130 <https://github.com/pytest-dev/pytest/issues/3130>_)

• The default cache directory has been renamed from .cache to
  .pytest_cache after community feedback that the name .cache did not
  make it clear that it was used by pytest. (3138 <https://github.com/pytest-dev/pytest/issues/3138>_)

• Colorize the levelname column in the live-log output. (3142 <https://github.com/pytest-dev/pytest/issues/3142>_)

Bug Fixes

• Fix hanging pexpect test on MacOS by using flush() instead of wait().
  (2022 <https://github.com/pytest-dev/pytest/issues/2022>_)

• Fix restoring Python state after in-process pytest runs with the
  pytester plugin; this may break tests using multiple inprocess
  pytest runs if later ones depend on earlier ones leaking global interpreter
  changes. (3016 <https://github.com/pytest-dev/pytest/issues/3016>_)

• Fix skipping plugin reporting hook when test aborted before plugin setup
  hook. (3074 <https://github.com/pytest-dev/pytest/issues/3074>_)

• Fix progress percentage reported when tests fail during teardown. (3088 <https://github.com/pytest-dev/pytest/issues/3088>_)

• Incompatible change: -o/--override option no longer eats all the
  remaining options, which can lead to surprising behavior: for example,
  pytest -o foo=1 /path/to/test.py would fail because /path/to/test.py
  would be considered as part of the -o command-line argument. One
  consequence of this is that now multiple configuration overrides need
  multiple -o flags: pytest -o foo=1 -o bar=2. (3103 <https://github.com/pytest-dev/pytest/issues/3103>_)

Improved Documentation

• Document hooks (defined with historic=True) which cannot be used with
  hookwrapper=True. (2423 <https://github.com/pytest-dev/pytest/issues/2423>_)

• Clarify that warning capturing doesn't change the warning filter by default.
  (2457 <https://github.com/pytest-dev/pytest/issues/2457>_)

• Clarify a possible confusion when using pytest_fixture_setup with fixture
  functions that return None. (2698 <https://github.com/pytest-dev/pytest/issues/2698>_)

• Fix the wording of a sentence on doctest flags used in pytest. (3076 <https://github.com/pytest-dev/pytest/issues/3076>_)

• Prefer https://*.readthedocs.io over http://*.rtfd.org for links in
  the documentation. (3092 <https://github.com/pytest-dev/pytest/issues/3092>_)

• Improve readability (wording, grammar) of Getting Started guide (3131 <https://github.com/pytest-dev/pytest/issues/3131>_)

• Added note that calling pytest.main multiple times from the same process is
  not recommended because of import caching. (3143 <https://github.com/pytest-dev/pytest/issues/3143>_)

Trivial/Internal Changes

• Show a simple and easy error when keyword expressions trigger a syntax error
  (for example, "-k foo and import" will show an error that you can not use
  the import keyword in expressions). (2953 <https://github.com/pytest-dev/pytest/issues/2953>_)

• Change parametrized automatic test id generation to use the __name__
  attribute of functions instead of the fallback argument name plus counter.
  (2976 <https://github.com/pytest-dev/pytest/issues/2976>_)

• Replace py.std with stdlib imports. (3067 <https://github.com/pytest-dev/pytest/issues/3067>_)

• Corrected 'you' to 'your' in logging docs. (3129 <https://github.com/pytest-dev/pytest/issues/3129>_)

3.3.2

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

Bug Fixes

• pytester: ignore files used to obtain current user metadata in the fd leak
  detector. (2784 <https://github.com/pytest-dev/pytest/issues/2784>_)

• Fix memory leak where objects returned by fixtures were never destructed
  by the garbage collector. (2981 <https://github.com/pytest-dev/pytest/issues/2981>_)

• Fix conversion of pyargs to filename to not convert symlinks on Python 2. (2985 <https://github.com/pytest-dev/pytest/issues/2985>_)

• PYTEST_DONT_REWRITE is now checked for plugins too rather than only for
  test modules. (2995 <https://github.com/pytest-dev/pytest/issues/2995>_)

Improved Documentation

• Add clarifying note about behavior of multiple parametrized arguments (3001 <https://github.com/pytest-dev/pytest/issues/3001>_)

Trivial/Internal Changes

• Code cleanup. (3015 <https://github.com/pytest-dev/pytest/issues/3015>,
  3021 <https://github.com/pytest-dev/pytest/issues/3021>)

• Clean up code by replacing imports and references of _ast to ast. (3018 <https://github.com/pytest-dev/pytest/issues/3018>_)

3.3.1

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

Bug Fixes

• Fix issue about -p no:<plugin> having no effect. (2920 <https://github.com/pytest-dev/pytest/issues/2920>_)

• Fix regression with warnings that contained non-strings in their arguments in
  Python 2. (2956 <https://github.com/pytest-dev/pytest/issues/2956>_)

• Always escape null bytes when setting PYTEST_CURRENT_TEST. (2957 <https://github.com/pytest-dev/pytest/issues/2957>_)

• Fix ZeroDivisionError when using the testmon plugin when no tests
  were actually collected. (2971 <https://github.com/pytest-dev/pytest/issues/2971>_)

• Bring back TerminalReporter.writer as an alias to
  TerminalReporter._tw. This alias was removed by accident in the 3.3.0
  release. (2984 <https://github.com/pytest-dev/pytest/issues/2984>_)

• The pytest-capturelog plugin is now also blacklisted, avoiding errors when
  running pytest with it still installed. (3004 <https://github.com/pytest-dev/pytest/issues/3004>_)

Improved Documentation

• Fix broken link to plugin pytest-localserver. (2963 <https://github.com/pytest-dev/pytest/issues/2963>_)

Trivial/Internal Changes

• Update github "bugs" link in CONTRIBUTING.rst (2949 <https://github.com/pytest-dev/pytest/issues/2949>_)

3.3.0

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

Deprecations and Removals

• Pytest no longer supports Python 2.6 and 3.3. Those Python versions
  are EOL for some time now and incur maintenance and compatibility costs on
  the pytest core team, and following up with the rest of the community we
  decided that they will no longer be supported starting on this version. Users
  which still require those versions should pin pytest to <3.3. (2812 <https://github.com/pytest-dev/pytest/issues/2812>_)

• Remove internal _preloadplugins() function. This removal is part of the
  pytest_namespace() hook deprecation. (2636 <https://github.com/pytest-dev/pytest/issues/2636>_)

• Internally change CallSpec2 to have a list of marks instead of a broken
  mapping of keywords. This removes the keywords attribute of the internal
  CallSpec2 class. (2672 <https://github.com/pytest-dev/pytest/issues/2672>_)

• Remove ParameterSet.deprecated_arg_dict - its not a public api and the lack
  of the underscore was a naming error. (2675 <https://github.com/pytest-dev/pytest/issues/2675>_)

• Remove the internal multi-typed attribute Node._evalskip and replace it
  with the boolean Node._skipped_by_mark. (2767 <https://github.com/pytest-dev/pytest/issues/2767>_)

• The params list passed to pytest.fixture is now for
  all effects considered immutable and frozen at the moment of the pytest.fixture
  call. Previously the list could be changed before the first invocation of the fixture
  allowing for a form of dynamic parametrization (for example, updated from command-line options),
  but this was an unwanted implementation detail which complicated the internals and prevented
  some internal cleanup. See issue 2959 <https://github.com/pytest-dev/pytest/issues/2959>_
  for details and a recommended workaround.

Features

• pytest_fixture_post_finalizer hook can now receive a request
  argument. (2124 <https://github.com/pytest-dev/pytest/issues/2124>_)

• Replace the old introspection code in compat.py that determines the available
  arguments of fixtures with inspect.signature on Python 3 and
  funcsigs.signature on Python 2. This should respect __signature__
  declarations on functions. (2267 <https://github.com/pytest-dev/pytest/issues/2267>_)

• Report tests with global pytestmark variable only once. (2549 <https://github.com/pytest-dev/pytest/issues/2549>_)

• Now pytest displays the total progress percentage while running tests. The
  previous output style can be set by configuring the console_output_style
  setting to classic. (2657 <https://github.com/pytest-dev/pytest/issues/2657>_)

• Match warns signature to raises by adding match keyword. (2708 <https://github.com/pytest-dev/pytest/issues/2708>_)

• Pytest now captures and displays output from the standard logging module.
  The user can control the logging level to be captured by specifying options
  in pytest.ini, the command line and also during individual tests using
  markers. Also, a caplog fixture is available that enables users to test
  the captured log during specific tests (similar to capsys for example).
  For more information, please see the logging docs <https://docs.pytest.org/en/latest/logging.html>. This feature was
  introduced by merging the popular pytest-catchlog <https://pypi.org/project/pytest-catchlog/> plugin, thanks to Thomas Hisch <https://github.com/thisch>. Be advised that during the merging the
  backward compatibility interface with the defunct pytest-capturelog has
  been dropped. (2794 <https://github.com/pytest-dev/pytest/issues/2794>)

• Add allow_module_level kwarg to pytest.skip(), enabling to skip the
  whole module. (2808 <https://github.com/pytest-dev/pytest/issues/2808>_)

• Allow setting file_or_dir, -c, and -o in PYTEST_ADDOPTS. (2824 <https://github.com/pytest-dev/pytest/issues/2824>_)

• Return stdout/stderr capture results as a namedtuple, so out and
  err can be accessed by attribute. (2879 <https://github.com/pytest-dev/pytest/issues/2879>_)

• Add capfdbinary, a version of capfd which returns bytes from
  readouterr(). (2923 <https://github.com/pytest-dev/pytest/issues/2923>_)

• Add capsysbinary a version of capsys which returns bytes from
  readouterr(). (2934 <https://github.com/pytest-dev/pytest/issues/2934>_)

• Implement feature to skip setup.py files when run with
  --doctest-modules. (502 <https://github.com/pytest-dev/pytest/issues/502>_)

Bug Fixes

• Resume output capturing after capsys/capfd.disabled() context manager.
  (1993 <https://github.com/pytest-dev/pytest/issues/1993>_)

• pytest_fixture_setup and pytest_fixture_post_finalizer hooks are now
  called for all conftest.py files. (2124 <https://github.com/pytest-dev/pytest/issues/2124>_)

• If an exception happens while loading a plugin, pytest no longer hides the
  original traceback. In Python 2 it will show the original traceback with a new
  message that explains in which plugin. In Python 3 it will show 2 canonized
  exceptions, the original exception while loading the plugin in addition to an
  exception that pytest throws about loading a plugin. (2491 <https://github.com/pytest-dev/pytest/issues/2491>_)

• capsys and capfd can now be used by other fixtures. (2709 <https://github.com/pytest-dev/pytest/issues/2709>_)

• Internal pytester plugin properly encodes bytes arguments to
  utf-8. (2738 <https://github.com/pytest-dev/pytest/issues/2738>_)

• testdir now uses use the same method used by tmpdir to create its
  temporary directory. This changes the final structure of the testdir
  directory slightly, but should not affect usage in normal scenarios and
  avoids a number of potential problems. (2751 <https://github.com/pytest-dev/pytest/issues/2751>_)

• Pytest no longer complains about warnings with unicode messages being
  non-ascii compatible even for ascii-compatible messages. As a result of this,
  warnings with unicode messages are converted first to an ascii representation
  for safety. (2809 <https://github.com/pytest-dev/pytest/issues/2809>_)

• Change return value of pytest command when --maxfail is reached from
  2 (interrupted) to 1 (failed). (2845 <https://github.com/pytest-dev/pytest/issues/2845>_)

• Fix issue in assertion rewriting which could lead it to rewrite modules which
  should not be rewritten. (2939 <https://github.com/pytest-dev/pytest/issues/2939>_)

• Handle marks without description in pytest.ini. (2942 <https://github.com/pytest-dev/pytest/issues/2942>_)

Trivial/Internal Changes

• pytest now depends on attrs <https://pypi.org/project/attrs/>_ for internal
  structures to ease code maintainability. (2641 <https://github.com/pytest-dev/pytest/issues/2641>_)

• Refactored internal Python 2/3 compatibility code to use six. (2642 <https://github.com/pytest-dev/pytest/issues/2642>_)

• Stop vendoring pluggy - we're missing out on its latest changes for not
  much benefit (2719 <https://github.com/pytest-dev/pytest/issues/2719>_)

• Internal refactor: simplify ascii string escaping by using the
  backslashreplace error handler in newer Python 3 versions. (2734 <https://github.com/pytest-dev/pytest/issues/2734>_)

• Remove unnecessary mark evaluator in unittest plugin (2767 <https://github.com/pytest-dev/pytest/issues/2767>_)

• Calls to Metafunc.addcall now emit a deprecation warning. This function
  is scheduled to be removed in pytest-4.0. (2876 <https://github.com/pytest-dev/pytest/issues/2876>_)

• Internal move of the parameterset extraction to a more maintainable place.
  (2877 <https://github.com/pytest-dev/pytest/issues/2877>_)

• Internal refactoring to simplify scope node lookup. (2910 <https://github.com/pytest-dev/pytest/issues/2910>_)

• Configure pytest to prevent pip from installing pytest in unsupported
  Python versions. (2922 <https://github.com/pytest-dev/pytest/issues/2922>_)

3.2.5

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

Bug Fixes

• Remove py<1.5 restriction from pytest as this can cause version
  conflicts in some installations. (2926 <https://github.com/pytest-dev/pytest/issues/2926>_)

3.2.4

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

Bug Fixes

• Fix the bug where running with --pyargs will result in items with
  empty parent.nodeid if run from a different root directory. (2775 <https://github.com/pytest-dev/pytest/issues/2775>_)

• Fix issue with pytest.parametrize if argnames was specified as keyword arguments.
  (2819 <https://github.com/pytest-dev/pytest/issues/2819>_)

• Strip whitespace from marker names when reading them from INI config. (2856 <https://github.com/pytest-dev/pytest/issues/2856>_)

• Show full context of doctest source in the pytest output, if the line number of
  failed example in the docstring is < 9. (2882 <https://github.com/pytest-dev/pytest/issues/2882>_)

• Match fixture paths against actual path segments in order to avoid matching folders which share a prefix.
  (2836 <https://github.com/pytest-dev/pytest/issues/2836>_)

Improved Documentation

• Introduce a dedicated section about conftest.py. (1505 <https://github.com/pytest-dev/pytest/issues/1505>_)

• Explicitly mention xpass in the documentation of xfail. (1997 <https://github.com/pytest-dev/pytest/issues/1997>_)

• Append example for pytest.param in the example/parametrize document. (2658 <https://github.com/pytest-dev/pytest/issues/2658>_)

• Clarify language of proposal for fixtures parameters (2893 <https://github.com/pytest-dev/pytest/issues/2893>_)

• List python 3.6 in the documented supported versions in the getting started
  document. (2903 <https://github.com/pytest-dev/pytest/issues/2903>_)

• Clarify the documentation of available fixture scopes. (538 <https://github.com/pytest-dev/pytest/issues/538>_)

• Add documentation about the python -m pytest invocation adding the
  current directory to sys.path. (911 <https://github.com/pytest-dev/pytest/issues/911>_)

3.2.3

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

Bug Fixes

• Fix crash in tab completion when no prefix is given. (2748 <https://github.com/pytest-dev/pytest/issues/2748>_)

• The equality checking function (__eq__) of MarkDecorator returns
  False if one object is not an instance of MarkDecorator. (2758 <https://github.com/pytest-dev/pytest/issues/2758>_)

• When running pytest --fixtures-per-test: don't crash if an item has no
  fixtureinfo attribute (e.g. doctests) (2788 <https://github.com/pytest-dev/pytest/issues/2788>)

Improved Documentation

• In help text of -k option, add example of using not to not select
  certain tests whose names match the provided expression. (1442 <https://github.com/pytest-dev/pytest/issues/1442>_)

• Add note in parametrize.rst about calling metafunc.parametrize
  multiple times. (1548 <https://github.com/pytest-dev/pytest/issues/1548>_)

Trivial/Internal Changes

• Set xfail_strict=True in pytest's own test suite to catch expected
  failures as soon as they start to pass. (2722 <https://github.com/pytest-dev/pytest/issues/2722>_)

• Fix typo in example of passing a callable to markers (in example/markers.rst)
  (2765 <https://github.com/pytest-dev/pytest/issues/2765>_)

pytest-mock 1.6.3 -> 1.7.1

1.7.1

---

• Fix setup.py to correctly read the README.rst. Thanks ghisvail_ for the fix (107_).

.. _107: pytest-dev/pytest-mock#107

1.7.0

---

Incompatible change

• pytest-mock no longer supports Python 2.6 and Python 3.3, following the lead of
  pytest and other projects in the community. Thanks hugovk_ for the PR (96_).

Packaging

• Fix mock requirement in Python 2. Thanks ghisvail_ for the report (101_).

Internal

• Some tests in pytest-mock's suite are skipped if assertion rewriting is disabled (102_).

.. _ghisvail: https://github.com/ghisvail
.. _hugovk: https://github.com/hugovk
.. _96: pytest-dev/pytest-mock#96
.. _101: pytest-dev/pytest-mock#101
.. _102: pytest-dev/pytest-mock#102

pytest-sugar 0.9.0 -> 0.9.1

0.9.1

^^^^^^^^^^^^^^^^^^^

• Fix incompatibility with pytest 3.4 (thanks nicoddemus)

That's it for now!

Happy merging! 🤖

[pyup-bot]

Closing this in favor of #55