Did I find the right examples for you? yes no

All Samples(8)  |  Call(0)  |  Derive(0)  |  Import(8)
Instances of the Logger class represent a single logging channel. A
"logging channel" indicates an area of an application. Exactly how an
"area" is defined is up to the application developer. Since an
application can have any number of areas, logging channels are identified
by a unique string. Application areas can be nested (e.g. an area
of "input processing" might include sub-areas "read CSV files", "read
XLS files" and "read Gnumeric files"). To cater for this natural nesting,
channel names are organized into a namespace hierarchy where levels are
separated by periods, much like the Java or Python package namespace. So
in the instance given above, channel names might be "input" for the upper(more...)

src/p/y/pylama-3.1.0/pylama/core.py   pylama(Download)
import logging
 
from .config import process_value, LOGGER
from .lint.extensions import LINTERS
 

src/p/y/pylama-HEAD/pylama/core.py   pylama(Download)
import logging
 
from .config import process_value, LOGGER
from .lint.extensions import LINTERS
 

src/c/o/collective.logbook-0.6/collective/logbook/utils.py   collective.logbook(Download)
from Products.CMFPlone.utils import safe_unicode
 
from config import LOGGER
 
REGEX = re.compile(r'0x[0-9a-fA-F]+')

src/c/o/collective.logbook-0.6/collective/logbook/monkey.py   collective.logbook(Download)
from Products.SiteErrorLog.SiteErrorLog import SiteErrorLog
 
from config import LOGGER
from events import ErrorRaisedEvent
 

src/c/o/collective.logbook-0.6/collective/logbook/events.py   collective.logbook(Download)
from Acquisition import aq_parent
 
from config import LOGGER
 
from interfaces import IErrorRaisedEvent