__future__.barry_as_FLUFL documented as mandatory for Python 3.9

[chris-rands]

BPO	35526
Nosy	@warsaw, @brettcannon, @vstinner, @benjaminp, @chris-rands
PRs	bpo-35526: make __future__.barry_as_FLUFL mandatory for Python 4.0 #11218

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2018-12-19.16:20:03.173>
created_at = <Date 2018-12-18.15:56:04.409>
labels = []
title = '__future__.barry_as_FLUFL documented as mandatory for Python 3.9'
updated_at = <Date 2018-12-20.05:39:47.848>
user = 'https://github.com/chris-rands'

bugs.python.org fields:

activity = <Date 2018-12-20.05:39:47.848>
actor = 'benjamin.peterson'
assignee = 'none'
closed = True
closed_date = <Date 2018-12-19.16:20:03.173>
closer = 'barry'
components = []
creation = <Date 2018-12-18.15:56:04.409>
creator = 'ChrisRands'
dependencies = []
files = []
hgrepos = []
issue_num = 35526
keywords = ['patch']
message_count = 5.0
messages = ['332068', '332069', '332075', '332148', '332174']
nosy_count = 5.0
nosy_names = ['barry', 'brett.cannon', 'vstinner', 'benjamin.peterson', 'ChrisRands']
pr_nums = ['11218']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue35526'
versions = []

[chris-rands]

A festive bug report:

>>> from __future__ import barry_as_FLUFL
>>> barry_as_FLUFL.mandatory
(3, 9, 0, 'alpha', 0)

So barry_as_FLUFL is documented to become mandatory for Python 3.9. Note that mandatory here means that the feature becomes permanent without the __future__ import and cannot be switched off. In this case, this means the '!=' operator becomes a SynaxError, with obvious consequences for existing python code.

Now of course this is just an Easter egg, but given that 3.9 is surely on the horizon now, isn't it time to modify the joke, or maybe I'm missing the point and the joke is on me?

[chris-rands]

SO question where this derived from:

https://stackoverflow.com/questions/53830960/can-all-future-statements-be-removed-from-a-python-code-without-affecting-i

[warsaw]

Let's extend the "joke" and make it mandatory in Python 4! :)

[warsaw]

New changeset 55cc345 by Barry Warsaw (Chris Rands) in branch 'master':
bpo-35526: make __future__.barry_as_FLUFL mandatory for Python 4.0 (bpo-11218)
55cc345

[benjaminp]

Good thing we don't need a barry_as_GUIDO alias.