This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients gmelikov, serhiy.storchaka
Date 2020-02-15.19:35:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581795340.27.0.98042771332.issue39640@roundup.psfhosted.org>
In-reply-to
Content
fsync() may be slower than fdatasync(). There may be cases in which you prefer to not call fsync() or call it less often if POSIX fdatasync() is not available. To do this you should know whether Python fdatasync() calls POSIX fdatasync() or fsync(). The simplest way to provide this information to user is to not provide os.fdatasync() in the underlying system call is not available.

Note also that this change will not help to run code with fdatasync() on MacOS without fallbacks in Python code until you drop support of all Python versions older than 3.9.
History
Date User Action Args
2020-02-15 19:35:40serhiy.storchakasetrecipients: + serhiy.storchaka, gmelikov
2020-02-15 19:35:40serhiy.storchakasetmessageid: <1581795340.27.0.98042771332.issue39640@roundup.psfhosted.org>
2020-02-15 19:35:40serhiy.storchakalinkissue39640 messages
2020-02-15 19:35:40serhiy.storchakacreate