Change by sebix :
--
nosy: +sebix
___
Python tracker
<https://bugs.python.org/issue13824>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
sebix added the comment:
> I suggest as a workaround that a context manager approach could be used to
> save and restore part of the logging configuration around various operations
> (at least levels and handlers), as outlined here:
> https://docs.python.org/3/howto/logging-c
sebix added the comment:
Oh, that's something different than I initially thought.
Using copy.deepcopy gives the same result as with copy.copy.
--
title: Different behavior of copied loggers in 3.7 -> copy.copy and deepcopy do
return same logger objects in 3.7
type: -&g
Change by sebix :
--
nosy: +sebix
___
Python tracker
<https://bugs.python.org/issue16468>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Change by sebix :
--
nosy: +sebix
___
Python tracker
<https://bugs.python.org/issue16878>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Change by sebix :
--
nosy: +sebix
___
Python tracker
<https://bugs.python.org/issue9625>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from sebix :
For the unittests of project I mock the function returning the logger. The code
to tests can re-initialize the logger because of updated configuration (It's a
deamon), so it needs to do that correctly and I test if it works. By mocking
the function returning
Change by sebix :
--
nosy: +sebix
___
Python tracker
<https://bugs.python.org/issue9338>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth