bpo-35781: Changed references to deprecated 'warn' method in logging documentation in favour of 'warning' (GH-11654)

This commit is contained in:
yuji38kwmt 2019-01-23 16:27:13 +09:00 committed by Vinay Sajip
parent f0c743604f
commit cda73a5af2
2 changed files with 4 additions and 4 deletions

View file

@ -186,7 +186,7 @@ previous simple module-based configuration example::
# 'application' code
logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.warning('warn message')
logger.error('error message')
logger.critical('critical message')
@ -295,7 +295,7 @@ Here is an example of a module using the logging configuration server::
while True:
logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.warning('warn message')
logger.error('error message')
logger.critical('critical message')
time.sleep(5)

View file

@ -610,7 +610,7 @@ logger, a console handler, and a simple formatter using Python code::
# 'application' code
logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.warning('warn message')
logger.error('error message')
logger.critical('critical message')
@ -640,7 +640,7 @@ the names of the objects::
# 'application' code
logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.warning('warn message')
logger.error('error message')
logger.critical('critical message')