You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the way that bup handles stdout/stderr is a little exotic. it seems to reopen file descriptors under certain circumstances.
this makes it difficult to make subcommands that want to process logging or handle those file descriptors differently. for example, i worked on a wrapper for index/save that redirects stdout to /dev/null (if not verbose) and stderr to a file for logging.
this yields various errors in the logs:
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
the way that bup handles stdout/stderr is a little exotic. it seems to reopen file descriptors under certain circumstances.
this makes it difficult to make subcommands that want to process logging or handle those file descriptors differently. for example, i worked on a wrapper for index/save that redirects stdout to /dev/null (if not verbose) and stderr to a file for logging.
this yields various errors in the logs:
now this may be a bug in python itself: http://bugs.python.org/issue11380
but it's unclear to me while those file descriptors are being messed with.
The text was updated successfully, but these errors were encountered: