Add a special case to the flag used before parsing/init message code to avoid calling logging.exception to log where it happened when the error itself originated from the pyglib.logging module.  Without this, an eventually terminating recursive dump of stack traces occurs when someone uses a logging method before parsing/init has happened.
Add a special case to the flag used before parsing/init message code to
avoid calling logging.exception to log where it happened when the error
itself originated from the pyglib.logging module.  Without this, an
eventually terminating recursive dump of stack traces occurs when someone
uses a logging method before parsing/init has happened.

While we frown on logging at import time or pre parsing/init in general, we
need to allow it and treat it similar to what C++ logging does: default
behaviors with output only to stderr.  Until we've cleaned the logging library
up for that, this prevents an uncomprehensible recursive exception error log.

	Change on 2016/09/21 by gps <gps@google.com>

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=133873557

gsutil-mirrors/python-gflags