Feature/issue184 loguru debug

[arkinn47]

Description

Summary of changes

• In the init.py file, in the torchquad folder, line 49, which called the set_log_level function was deleted.
• On lines 3 and 4, a commented line of explanation and the function "logger.disable("torchquad")" were added respectively.
• A test file logger_test.py was also added in the main folder, which runs a unit test testing if logger works.

Resolved Issues

• fixes #Issue 184, where when torchquad is imported logger does not properly log ie. logger.info("..."), does not print anything.

How Has This Been Tested?

• Test A: The test import torchquad and then attempts to write a log with logger.info and then checks if it was logged.

Related Pull Requests

• #PR

[gomezzz]

Hi @arkinn47 !

Thanks for the PR, I think this could work! However, I think the problem is slightly more involved than this. Right now, we are using loguru also to display error messages to user via https://github.com/search?q=repo%3Aesa%2Ftorchquad%20logger.error&type=code and https://github.com/search?q=repo%3Aesa%2Ftorchquad+logger.warning&type=code .

• With logger.disable these would not be shown anymore, so I think we need to change those occurrences then to use something else?
• Ideally we would set logger.disable only in release builds since we want logs for debugging. If we can't automate, we should at least mention it in contribute or similar? What do you think?

Thanks!