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 steve.dower
Recipients ishimoto, ocean-city, paul.moore, pitrou, schmir, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2018-08-15.15:40:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534347645.81.0.56676864532.issue2122@psf.upfronthosting.co.za>
In-reply-to
Content
I agree. We should definitely document it as a change, but I don't think there's anything useful you can do in the case of a flush failing anyway, so it seems unlikely that anyone could depend on the return value.

Returning None for success and exception on error sounds like a good change. Technically this is no longer returning zero, as previously documented, so if anyone wants to get *really* pedantic, we're not returning the "failed" result for success ;)
History
Date User Action Args
2018-08-15 15:40:45steve.dowersetrecipients: + steve.dower, paul.moore, ishimoto, pitrou, ocean-city, schmir, tim.golden, zach.ware, serhiy.storchaka
2018-08-15 15:40:45steve.dowersetmessageid: <1534347645.81.0.56676864532.issue2122@psf.upfronthosting.co.za>
2018-08-15 15:40:45steve.dowerlinkissue2122 messages
2018-08-15 15:40:45steve.dowercreate