11/29/2023 0 Comments Log guru![]() ![]() 15:19:50.205 | SUCCESS | _mp_main_:worker:14 - My function executed successfully 15:19:49.205 15:19:49.205 | | SUCCESS SUCCESS | | _mp_main_mp_main_::workerworker::1414 - My function executed successfullyMy function executed successfully Is this the intended behavior? 15:19:49.197 | SUCCESS | _mp_main_:worker:14 - My function executed successfully I am trying to log to sys.stderr using multiprocessing but the log messages are getting overlapped. Logger.addHandler(logging.StreamHandler()) Steps to Reproduce Base test file # test_demo.py Actual ResultÄrop-in replacement causes tests that use the caplog pytest fixture to fail. Users should be able to use loguru as a drop-in replacement for the stdlib logging package and have tests that use the caplog fixture still work. ![]() I'm not sure if this is user error (perhaps it's documented somewhere? I haven't been able to find it.), if it is some design oversight/choice, or if the problem is actually on pytest's end. ![]() I'd love to move to loguru, but loguru doesn't seem to work with caplog. Pytest's caplog fixture is a critical part of testing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |