[issue7360] [mailbox] race: mbox may lose data with concurrent access

Petri Lehtinen added the comment: I created #15122 for adding an option to rewrite the contents of single-file mailboxes in-place. Closing this issue as wontfix. -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed superseder: -> Add an option to always rew

[issue7360] [mailbox] race: mbox may lose data with concurrent access

R. David Murray added the comment: Probably. Unless I'm mistaken, the issue with concurrent rewrite (as opposed to append) exists for single-file-mailboxes in the general case, not just in Python. And as far as I know failure is never noisy, the last writer wins. -- nosy: +r.david.m

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Petri Lehtinen added the comment: Can this be closed? -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Changes by Antoine Pitrou : -- nosy: +akuchling ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Antoine Pitrou added the comment: Actually, the doc is quite clear about it: « Be very cautious when modifying mailboxes that might be simultaneously changed by some other process. The safest mailbox format to use for such tasks is Maildir; try to avoid using single-file formats such as mbox fo

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Antoine Pitrou added the comment: Oops, sorry: > I don't think this class aims at being safe against concurrent access, > so having it fail loudly is a good thing. I now understand that the problem is that it doesn't fail loudly. That's what I get for replying too quickly. Still, I don't think

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Antoine Pitrou added the comment: > the mailbox._singlefileMailbox class is not safe with concurrent access, > because mailbox._singlefileMailbox.flush() replaces the underlying file > with a new copy by constructing a temporary file and then renaming it. > This breaks all other class instances

[issue7360] [mailbox] race: mbox may lose data with concurrent access

Changes by Matthias Klose : Added file: http://bugs.python.org/file15364/mailbox-race.py ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue7360] [mailbox] race: mbox may lose data with concurrent access

New submission from Matthias Klose : [forwarded from http://bugs.debian.org/451733] the mailbox._singlefileMailbox class is not safe with concurrent access, because mailbox._singlefileMailbox.flush() replaces the underlying file with a new copy by constructing a temporary file and then renaming