Oct. 19, 2021
2:05 a.m.
On Tue, Oct 19, 2021 at 11:30 AM Jeremiah Paige <ucodery@gmail.com> wrote:
This could probably be toggled via a __future__ import which would make its usage more apparent to readers of the file. But this would imply that the keyword would eventually be turned on by default; I don't think there are any examples of __future__ imports intended to be left forever as options for the programmer.
Aside from barry_as_FLUFL, which doesn't really count, no - they all have clearly-defined end dates after which they remain syntactically valid but have no effect. ChrisA