muon
muon copied to clipboard
unify logging
We didn't establish a clear policy around logging early on, so now some parts of muon use Scanpy's logger, while others issue plain warnings using the warnings module. Ideally, this should be unified, one way or another.
There are at least these options to consider, I assume:
- built-in Python
logging, - scanpy
logging, configurable throughscanpy.settings.verbosity, - re-using scanpy
logginginternals but make it configurable throughmuon.set_options.
I would lean towards the last option since I would not expect scanpy.settings.verbosity to affect another package and I would also expect to be able to tune it separately if needed. I can expect it would frequently mean defining verbosity options across two lines instead of a single line of code but it seems to me more explicit and hence better.
Any thoughts?