[Python-Dev] barry_as_FLUFL

[Guido van Rossum]

On Wed, Aug 4, 2010 at 3:48 PM, Jasper St. Pierre <jstpierre at mecheye.net> wrote:
> 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.

We don't revert our April Fool's checkins. Easter eggs are forever!

-- 
--Guido van Rossum (python.org/~guido)