-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate Logging from PyStell-UW #89
Comments
Here's the most promising solution I could find. Unfortunately, I don't think that PyStell-UW's logging is handled by the logger manager, since it seems the logger dictionary mentioned in the article only contains logger objects, which PyStell-UW doesn't create. Here's the output from printing the logger dictionary, in case I'm missing something:
|
I think it makes sense to PR into pystell_UW to introduce logger objects... |
It seems that logging to the command line is being duplicated, as exemplified below:
I believe this issue is stemming from PyStell-UW since the logging format of the duplicate lines follow that specified in
read_vmec.py
, exemplified by the first logging output line,WARNING:root:...
, which is raised inread_vmec.py
. Moreover, this issue does not occur when using ParaStell functionality that does not rely on PyStell-UW (e.g., a script that only importsmagnet_coils
).Poking around in
read_vmec.py
a bit, I think the issue is that its logging does not occur via aLogger
object, but rather directly usinglogging
function calls (e.g.,logging.warning(...)
,logging.error(...)
, etc.).If need be, I can create an issue or PR in PyStell-UW but in the interest of expediency, I'm hoping there's a solution I can implement in ParaStell instead. I haven't been able to find anything online so far.
The text was updated successfully, but these errors were encountered: