Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add a custom "TRACE" log level for even more verbosity. #4672
Import logging as usual and within the galaxy namespace you should be able to use it with log.trace().
Includes one example swapping a statement over.
I found the existing NullHandler logging bits in
Can we do this differently - this is some nice magic and it works well for "Galaxy the application" - it is very elegant. The downside is I don't think monkey patching a standard library module is a good behavior for a library - so I'd like not to do this in galaxy-lib for instance. I'd prefer not not monkey the logger and just import a "trace" function from the
If I'm voted down on this can we at least allow both methods of tracing and then use the alternative, less elegant galaxy.util.trace for methods in galaxy-lib?
Oct 4, 2017
6 checks passed
So, one side effect of this change is that when switching from
It can also be worked around by backporting
We could also add the
I dunno about backporting the fix or renaming it, since this is just a temporary 'problem'. The naming seems right as-is, and you're right, the backport doesn't really feel like a stable bugfix.
One option is a commit hook to act on changing branches, but those aren't really easily shared :/
edit: I definitely do feel like we had this happen in the past and we just used it as a moment to educate folks (developers encountering it) about how to clean up old .pyc.