➜

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 petr.viktorin
Recipients Eric Appelt, barry, brett.cannon, doko, eric.snow, ishcherb, lukasz.langa, mark.dickinson, ncoghlan, petr.viktorin, serhiy.storchaka
Date 2017-02-13.14:02:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486994543.04.0.0356726014674.issue29514@psf.upfronthosting.co.za>
In-reply-to
Content 
In Fedora also want to stay close to upstream: every downstream patch is like an open issue, something we'd like to merge given enough time and people. But, for a problem that:
- is fixed in the latest version (3.6)
- is getting a test to not happen again
- only affects downstream distributions
I'm fine with a downstream patch.

I'd also be happy to work on making the patch acceptable upstream, but I need to hear some core devs' expectations on that. Where on the spectrum from throwaway hack to full-scale mechanism for accepting ranges of magic numbers should such a patch patch be?
History
Date User Action Args
2017-02-13 14:02:23petr.viktorinsetrecipients: + petr.viktorin, barry, brett.cannon, doko, mark.dickinson, ncoghlan, lukasz.langa, eric.snow, serhiy.storchaka, Eric Appelt, ishcherb
2017-02-13 14:02:23petr.viktorinsetmessageid: <1486994543.04.0.0356726014674.issue29514@psf.upfronthosting.co.za>
2017-02-13 14:02:23petr.viktorinlinkissue29514 messages
2017-02-13 14:02:22petr.viktorincreate