Hi, I'm currently using this package to power a tool in UCSF ChimeraX but I'm finding that it prints a lot of information to our log, which captures print statements and redirects them to itself.
It would be nice to go through the logging module instead, so that I (and other consumers) could do something like
to silence output messages, as we do with other libraries we use.
I am 100% willing to write the PR if you're amenable to the change, I just thought starting with an issue would be less presumptuous than a PR out of nowhere.
Hi, I'm currently using this package to power a tool in UCSF ChimeraX but I'm finding that it prints a lot of information to our log, which captures print statements and redirects them to itself.
It would be nice to go through the logging module instead, so that I (and other consumers) could do something like
to silence output messages, as we do with other libraries we use.
I am 100% willing to write the PR if you're amenable to the change, I just thought starting with an issue would be less presumptuous than a PR out of nowhere.