A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-August/102873.html below:

[Python-Dev] barry_as_FLUFL

[Python-Dev] barry_as_FLUFLJasper St. Pierre jstpierre at mecheye.net
Thu Aug 5 00:48:39 CEST 2010
I was fooling around with Python 3.1 today, and I found this little nugget:

>>> import __future__
>>> dir(__future__)
['CO_FUTURE_ABSOLUTE_IMPORT', 'CO_FUTURE_BARRY_AS_BDFL',
'CO_FUTURE_DIVISION', 'CO_FUTURE_PRINT_FUNCTION',
'CO_FUTURE_UNICODE_LITERALS', 'CO_FUTURE_WITH_STATEMENT',
'CO_GENERATOR_ALLOWED', 'CO_NESTED', '_Feature', '__all__',
'__builtins__', '__doc__', '__file__', '__name__', '__package__',
'absolute_import', 'all_feature_names', 'barry_as_FLUFL', 'division',
'generators', 'nested_scopes', 'print_function', 'unicode_literals',
'with_statement']

hmm... BARRY_AS_BDFL and barry_as_FLUFL

>>> from __future__ import barry_as_FLUFL
>>>

nothing noticable happened. I googled the latter, and found that it's an April
Fools (of 2009!) checkin that was never reverted.

http://mail.python.org/pipermail/python-checkins/2009-April/080796.html
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4