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 bquinlan
Recipients Steven.Barker, bquinlan, ned.deily
Date 2019-07-01.22:32:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANiivorDru=3h2Hj3kYAT6sajn9uABWEZCK+rdQ91pb1f8z9ow@mail.gmail.com>
In-reply-to <1562019933.78.0.110656318344.issue31783@roundup.psfhosted.org>
Content
I don't know what the backport policy is. The bug is only theoretical AFAIK
i.e. someone noticed it through code observation but it has not appeared in
the wild.

On Mon, Jul 1, 2019 at 3:25 PM Ned Deily <report@bugs.python.org> wrote:

>
> Ned Deily <nad@python.org> added the comment:
>
> Brian, should this fix be backported to 3.8 and 3.7?  As it stands now, it
> will only be showing up in Python 3.9 unless you add the backport labels to
> the original PR.  Unless it cna be shown to be a security issue, it would
> not be appropriate to backport to 3.6 at this stage.
>
> ----------
> nosy: +ned.deily
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue31783>
> _______________________________________
>
>
History
Date User Action Args
2019-07-01 22:32:23bquinlansetrecipients: + bquinlan, ned.deily, Steven.Barker
2019-07-01 22:32:23bquinlanlinkissue31783 messages
2019-07-01 22:32:23bquinlancreate