Re: FileNotFoundError thrown due to file name in file, rather than file itself

On 11/13/24 23:03, Left Right via Python-list wrote:
 >> On any Unix system this is untrue.  Rotating a log file is quite simple:
 >
 > I realized I posted this without cc'ing the list:
 > http://jdebp.info/FGA/do-not-use-logrotate.html .
 >
 > The link above gives a more detailed description of why log rotation
 > on the Unix system is not only not simple, but is, in fact,
 > unreliable.
Having read the linked article, I see it is not relevant to Python, as Python's logging tool is
the writer/rotator program, thus no window for lost entries exists.
 > NB. Also, it really rubs me the wrong way when the word "standard" is
 > used to mean "common" (instead of "as described in a standard
 > document").
Yes, that is irritating.
 >  And when it comes to popular tools, oftentimes "common"
 > is wrong because commonly the tool is used by amateurs rather than
 > experts.  In other words, you only reinforced what I wrote initially:
 > plenty of application developers don't know how to do logging well.
 > It also appears that they would lecture infra / ops people on how to
 > do something that they aren't experts on, while the latter are :)
Well, since this is a Python list, perhaps you could make sure your advice is also Python appropriate.  I appreciate diversions into general areas and learning new things, but your general claims were untrue when it comes to Python specifically, and that was unclear until I read your linked post.
--
~Ethan~