Steve R. Hastings added the comment:
I just reviewed the Python 3.6 logging code. Unless I am mistaken, it still
has the limitation that when a logging file is active for writing log events,
that file always has the same filename (self.baseFilename). Did I overlook
anything?
At rotation
Steve R. Hastings added the comment:
The solution recommended in the logging cookbook does not do the same thing as
I have proposed.
I have proposed a logging handler that emits JSON suitable for ingestion by a
log collection system. With the JSON formatter, all log events, no matter
their
Steve R. Hastings added the comment:
> What about [ BaseRotatingHandler.namer ] which allows you to specify your own
> naming scheme?
I confess that I overlooked that; it was added later than the version of Python
in which I wrote my original code.
The current Python code still has a
New submission from Steve R. Hastings :
Many logging aggregation and indexing systems require that log data must be
written in an easy-to-parse format such as JSON. A "batteries included" JSON
log formatter would be a useful enhancement.
I have written code with the following feat
New submission from Steve R. Hastings :
Python logging is not multi-process safe. When a Python program has multiple
processes, one way to log safely would be to put the process ID number into the
filename of the log file, giving each process its own log file.
It would be convenient if a %p
New submission from Steve R. Hastings :
When a logged file has a timed rotation, it is renamed with an archival
filename that includes a timestamp. The logging library has a small set of
predefined filename templates and no way is provided to override them.
Also, the current rule is that
New submission from Steve R. Hastings:
The normal build should not have any warnings. The source for libffi included
some comparisons between signed int and unsigned int, which caused warnings.
The patch changes the signed int variables to unsigned int.
--
components: Build
files
