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 ned.deily
Recipients Steven.Barker, bquinlan, ned.deily
Date 2019-07-01.22:55:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562021703.37.0.986022539496.issue31783@roundup.psfhosted.org>
In-reply-to
Content
> I don't know what the backport policy is.

It does seem that the devguide does not give much guidance on this; I've opened an issue about it (https://github.com/python/devguide/issues/503).  But, in general, if the fix is potentially beneficial and does not add undue risk or an incompatibility, we would generally consider backporting it to the currently active maintenance branches; at the moment, that would be 3.8 (in beta phase) and 3.7 (maintenance nmode).  We have a lot of buildbot tests that show non-deterministic failures, some possibly due to concurrent.futures.  If there is a chance that this fix might mitigate those, I'd like to consider it for backporting.
History
Date User Action Args
2019-07-01 22:55:03ned.deilysetrecipients: + ned.deily, bquinlan, Steven.Barker
2019-07-01 22:55:03ned.deilysetmessageid: <1562021703.37.0.986022539496.issue31783@roundup.psfhosted.org>
2019-07-01 22:55:03ned.deilylinkissue31783 messages
2019-07-01 22:55:03ned.deilycreate