Can Ren'Py Persistent Write Retry Count Be Configured?

Persistent Write Retry Logic

Ren'Py’s save system uses renpy.storage.safe_write to protect persistent data from transient I/O failures. The function retries the write operation up to a hard‑coded limit before raising an IOError. While the retry loop avoids re‑serializing the data, the documentation does not state that the operation is atomic or that duplicate records can never be created if a retry succeeds after a partial write.

Unresolved Decision

Because the retry count is embedded in the source, developers cannot change it at runtime. This raises questions about whether Ren'Py should expose a configurable retry policy for persistent saves.

• What is the current retry limit for persistent writes?
• Does Ren'Py guarantee that no duplicate persistent entries are created when a retry succeeds after a partial write?
• Is there a planned or possible way to expose the retry count as a configurable parameter?