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

Pin pytest-catchlog to latest version 1.2.2 #18

Merged
merged 1 commit into from
Aug 13, 2021

Conversation

pyup-bot
Copy link
Collaborator

This PR pins pytest-catchlog to the latest release 1.2.2.

Changelog

1.2.2

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

Released on 2016-01-24 UTC.

- [Bugfix] `30`_ `31`_ - Fix ``unicode`` vs ``str`` compatibility issues between Python2 and Python3.
(Thanks goes to `sirex`_ for reporting the issue and providing a fix!)

.. _30: https://github.com/eisensheng/pytest-catchlog/issues/30
.. _31: https://github.com/eisensheng/pytest-catchlog/issues/31
.. _sirex: https://github.com/sirex

1.2.1

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

Released on 2015-12-07.

- [Bugfix] 18 - Allow ``caplog.records()`` to be modified.  Thanks to Eldar Abusalimov for the PR and Marco Nenciarini for reporting the issue.
- [Bugfix] 15 17 - Restore Python 2.6 compatibility. (Thanks to Marco Nenciarini!)

.. attention::
 Deprecation warning: the following objects (i.e. functions, properties)
 are slated for removal in the next major release.

 - ``caplog.at_level`` and ``caplog.set_level`` should be used instead of
   ``caplog.atLevel`` and ``caplog.setLevel``.

   The methods ``caplog.atLevel`` and ``caplog.setLevel`` are still
   available but deprecated and not supported since they don't follow
   the PEP8 convention for method names.

 - ``caplog.text``, ``caplog.records`` and
   ``caplog.record_tuples`` were turned into properties.
   They still can be used as regular methods for backward compatibility,
   but that syntax is considered deprecated and scheduled for removal in
   the next major release.

1.2

-----------

Released on 2015-11-08.

- [Feature] 6 - Configure logging message and date format through ini file.
- [Feature] 7 - Also catch logs from setup and teardown stages.
- [Feature] 7 - Replace deprecated ``__multicall__`` use to support future Py.test releases.
- [Feature] 11 - reintroduce ``setLevel`` and ``atLevel`` to retain backward compatibility with pytest-capturelog.  Also the members ``text``, ``records`` and ``record_tuples`` of the ``caplog`` fixture can be used as properties now.

Special thanks for this release goes to Eldar Abusalimov.  He provided all of the changed features.

1.1

-----------

Released on 2015-06-07.

- 2 - Explicitly state Python3 support and add configuration for running
tests with tox on multiple Python versions. (Thanks to Jeremy Bowman!)
- Add an option to silence logs completely on the terminal.

1.0

-----------

Released on 2014-12-08.

- Add ``record_tuples`` for comparing recorded log entries against expected
log entries with their logger name, severity and formatted message.
Links

@codecov
Copy link

codecov bot commented Aug 13, 2021

Codecov Report

Merging #18 (c49c5ac) into master (de823a4) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #18   +/-   ##
=======================================
  Coverage   74.61%   74.61%           
=======================================
  Files           4        4           
  Lines         197      197           
=======================================
  Hits          147      147           
  Misses         50       50           

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 de823a4...c49c5ac. Read the comment docs.

@aragilar
Copy link
Owner

bors r+

@bors
Copy link
Contributor

bors bot commented Aug 13, 2021

Build succeeded:

@bors bors bot merged commit a59574a into master Aug 13, 2021
@aragilar aragilar deleted the pyup-pin-pytest-catchlog-1.2.2 branch August 14, 2021 04:14
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