Author gvanrossum
Recipients eric.smith, gvanrossum, levkivskyi, lukasz.langa, vstinner
Date 2019-10-27.23:23:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKBq_4S2XjsLKvcegxVbVHcsGbf7g-uduAeWkdyJ_MmDQ@mail.gmail.com>
In-reply-to <1572216705.82.0.609942732916.issue38605@roundup.psfhosted.org>
Content
We never should have mentioned 4.0 as the target date to make this the
default (and only) behavior -- who knows whether there will ever even be a
Python 4.0? Even 3.10 might be on the early side (assuming we'll switch to
a year-long release cycle per PEP 602 -- we will then make deprecations in
general take two release cycles).

I do agree that we should start the process of deprecating the
non-__future__ behavior here in 3.9. I know of one project with a private
fork of Python (for other reasons) that has made this default.
History
Date User Action Args
2019-10-27 23:23:41gvanrossumsetrecipients: + gvanrossum, vstinner, eric.smith, lukasz.langa, levkivskyi
2019-10-27 23:23:41gvanrossumlinkissue38605 messages
2019-10-27 23:23:41gvanrossumcreate