[issue37117] Simplify customization of the logging time through datefmt

Change by Vinay Sajip : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue37117] Simplify customization of the logging time through datefmt

Mario Corchero added the comment: > What do you mean by "it is not documented"? It is documented here: As it says: "This function uses a user-configurable function to convert the creation time to a tuple. By default, time.localtime() is used; to change this for a particular formatter

[issue37117] Simplify customization of the logging time through datefmt

Vinay Sajip added the comment: > AFAIK, the converter attribute is only to "be set" with a function of such > signature. It is not documented that it can be used and it is only used on > the format time function. What do you mean by "it is not documented"? It is documented here:

[issue37117] Simplify customization of the logging time through datefmt

Mario Corchero added the comment: AFAIK, the converter attribute is only to "be set" with a function of such signature. It is not documented that it can be used and it is only used on the format time function. The only situation where this might break someone is if they inherit from

[issue37117] Simplify customization of the logging time through datefmt

Vinay Sajip added the comment: The documentation mentions that the converter attribute of the formatter should be signature-compatible with time.localtime() and time.gmtime(), and some users will have set this attribute with one or the other or a compatible function. Doesn't your change

[issue37117] Simplify customization of the logging time through datefmt

New submission from Mario Corchero : Users that want to provide a custom template for the timestamp part of logging cannot customize the milliseconds part of asctime. They can use the msecs attribute of the Logger but that effectively requires to break the formatting in two parts. Note that