[issue42378] logging reopens file with same mode, possibly truncating

Vinay Sajip added the comment: New changeset e35430bec528dfb1a653cd457ea58b5a08543632 by Miss Islington (bot) in branch '3.10': [3.10] bpo-42378: fixed log truncation on logging shutdown (GH-27310) (GH-30468) https://github.com/python/cpython/commit/e35430bec528dfb1a653cd457ea58b5a08543632

[issue42378] logging reopens file with same mode, possibly truncating

Change by miss-islington : -- pull_requests: +28671 pull_request: https://github.com/python/cpython/pull/30468 ___ Python tracker ___ __

[issue42378] logging reopens file with same mode, possibly truncating

Vinay Sajip added the comment: I guess it got missed during the 3.10 beta cycle by not being backported - it might have needed to be cherry-picked. I'll see about getting it backported to 3.10. -- ___ Python tracker

[issue42378] logging reopens file with same mode, possibly truncating

Change by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue42378] logging reopens file with same mode, possibly truncating

Dustin Oprea added the comment: <- I'm intentionally using mode 'w' (to support development) and it's never been an issue until I recently refactored the project to be asynchronous. Now, every time I fail, I suddenly lose the logs. Not awesome. -- ___

[issue42378] logging reopens file with same mode, possibly truncating

Dustin Oprea added the comment: I believe I'm seeing this, still, in an async situation. It seems like the obvious culprit. When will this go out in a release? I'm on 3.10.1 from December (under Arch). The PR got merged to master in July but I went through all changelogs back to March and

[issue42378] logging reopens file with same mode, possibly truncating

miss-islington added the comment: New changeset 96cf5a63d2dbadaebf236362b4c7c09c51fda55c by andrei kulakov in branch 'main': bpo-42378: fixed log truncation on logging shutdown (GH-27310) https://github.com/python/cpython/commit/96cf5a63d2dbadaebf236362b4c7c09c51fda55c -- nosy: +mis

[issue42378] logging reopens file with same mode, possibly truncating

Andrei Kulakov added the comment: I've put up a PR here: https://github.com/python/cpython/pull/27310/files If this looks good, I will update the docs and add news entry. -- ___ Python tracker _

[issue42378] logging reopens file with same mode, possibly truncating

Change by Andrei Kulakov : -- keywords: +patch nosy: +andrei.avk nosy_count: 1.0 -> 2.0 pull_requests: +25855 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27310 ___ Python tracker

[issue42378] logging reopens file with same mode, possibly truncating

New submission from Ed Catmur : If a logging.FileHandler is configured with mode='w', or if logging.basicConfig is called with filemode='w' (as suggested by the Basic Logging Tutorial https://docs.python.org/3/howto/logging.html#logging-basic-tutorial) and if some code logs during shutdown, af