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 sylvain.corlay
Recipients Chip Lynch, efiop, emanuel, eryksun, gregory.p.smith, paul.moore, steve.dower, sylvain.corlay, tim.golden, vstinner, zach.ware
Date 2020-05-29.17:47:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAK=Phk45vJqty32dLbDVh=nBvA+ad7VjWuUKZ+2TE=nNhFqd6Q@mail.gmail.com>
In-reply-to <1590773344.2.0.54481947952.issue37380@roundup.psfhosted.org>
Content
Yes, I understand that.

I was wondering if there was a workaround that we could use to not drop 3.6
support right away!

On Fri, May 29, 2020, 19:29 STINNER Victor <report@bugs.python.org> wrote:

>
> STINNER Victor <vstinner@python.org> added the comment:
>
> Sadly, 3.6 no longer get bug fixes, only security fixes:
> https://devguide.python.org/#status-of-python-branches
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue37380>
> _______________________________________
>
History
Date User Action Args
2020-05-29 17:47:48sylvain.corlaysetrecipients: + sylvain.corlay, gregory.p.smith, paul.moore, vstinner, tim.golden, zach.ware, eryksun, steve.dower, efiop, emanuel, Chip Lynch
2020-05-29 17:47:48sylvain.corlaylinkissue37380 messages
2020-05-29 17:47:48sylvain.corlaycreate