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 process, processName, thread, and threadName fields are not currently considered valid by ZConfig.
These may, individually, be None or a value of the appropriate type, depending on the values of globals in the logging module.
This is at least tangentially related to #53, but may require special consideration given the relation to the logging.logThreads and logging.logMultiprocessing settings.
The text was updated successfully, but these errors were encountered:
funcName is another that's been omitted; it wasn't around when ZConfig was written, but has been since Python 2.6.
That one should be very safe to add a string sample value; it appears to always be present as a string, even though it might be an uninformative '(unknown function)' at times.
All of these fields are actually present when configuring a formatter using the defined sections, so validation of the fields works as expected, with the default settings of logging.logMultiprocessing and logging.logThreads.
The old validation function for format strings does not support these, though the updates to reflect proper types for other fields affect it as well.
- field added to log records in Python 2.6 and 3.1,
so accepted for all python versions supported by
ZConfig
- added tests specifically for the log_format function
accepting "funcName" and numeric formatting for
other fields recently touched in ZConfig
partially addresses issue #63
The
process
,processName
,thread
, andthreadName
fields are not currently considered valid byZConfig
.These may, individually, be
None
or a value of the appropriate type, depending on the values of globals in thelogging
module.This is at least tangentially related to #53, but may require special consideration given the relation to the
logging.logThreads
andlogging.logMultiprocessing
settings.The text was updated successfully, but these errors were encountered: