Brian Quinlan <br...@sweetapp.com> added the comment:
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 <rep...@bugs.python.org> wrote: > > Ned Deily <n...@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 <rep...@bugs.python.org> > <https://bugs.python.org/issue31783> > _______________________________________ > > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31783> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
