|
|
|
|
|
by mdaniel
324 days ago
|
|
I don't believe that "from __future__" is the future-proofing you think it is, they just named it that way to be cute - a hypothetical 3.19 version couldn't even use it, since it's just a normal python import $ python3.13 -c 'from __future__ import awesome_feature'
File "<string>", line 1
SyntaxError: future feature awesome_feature is not defined
the very idea of "future feature is not defined" is insaneoAnyway, I'd guess what they intend is try:
from __future__ import fever_dream
except SyntaxError:
fever_dream = None
because python really gets off on conditional imports |
|