➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author uosiu
Recipients Yoichi Nakayama, iritkatriel, michael.foord, pitrou, uosiu
Date 2021-02-22.09:17:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADp+y_HABH_jjzXX9kZZ06eovv5VSggJn2CW+3pNgNF5BCczEw@mail.gmail.com>
In-reply-to <1613586372.94.0.0683383549754.issue26600@roundup.psfhosted.org>
Content 
However there is still nothing in the docs that you have to mock `__str__`
by yourself
when using mock object with multiple threads. Otherwise calling `__str__`
may result
with raising exception if you are unlucky.

Stanisław Skonieczny

On Wed, Feb 17, 2021 at 7:26 PM Irit Katriel <report@bugs.python.org> wrote:

>
> Irit Katriel <iritkatriel@yahoo.com> added the comment:
>
> The documentation has examples how to set up a mock's __str__.
>
> https://docs.python.org/3/library/unittest.mock.html
>
> ----------
> nosy: +iritkatriel
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue26600>
> _______________________________________
>
History
Date User Action Args
2021-02-22 09:17:08uosiusetrecipients: + uosiu, pitrou, michael.foord, Yoichi Nakayama, iritkatriel
2021-02-22 09:17:07uosiulinkissue26600 messages
2021-02-22 09:17:07uosiucreate