Well, if we're at the "bikeshedding about names" stage, that means that no
serious issues with the proposal are left. So it's a sign of progress.
On Wed, Jan 9, 2013 at 12:42 AM, Stephen J. Turnbull wrote:
> Is this thread really ready to migrate to python-dev when we're still
> bikeshedding met
On Fri, Dec 21, 2012 at 8:02 PM, Guido van Rossum wrote:
... snip ...
In PEP 3156 conformant code you're supposed always to use 'yield
> from'. The only time you see a bare yield is when it's part of the
> implementation's internals. (However I think tulip actually will
> handle a yield the same
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_A
