Python: language moratorium is lifted(article.gmane.org) |
Python: language moratorium is lifted(article.gmane.org) |
PEP 380 (http://www.python.org/dev/peps/pep-0380/) would provide a convenient way for one generator function to yield all the values of another as part of its work. At the moment you have to say something like
for x in foo:
yield x
PEP 3152 (http://www.python.org/dev/peps/pep-3152/) uses the generator mechanism (as enhanced by PEP 380) which already provides something rather like coroutines, and adds some syntactic sugar to let you write coroutines that look like coroutines.
This PEP proposes a temporary moratorium (suspension) of all changes to the Python language syntax, semantics, and built-ins for a period of at least two years from the release of Python 3.1. In particular, the moratorium would include Python 3.2 (to be released 18-24 months after 3.1) but allow Python 3.3 (assuming it is not released prematurely) to once again include language changes.
Python 3.2 is newly released and 3.3 development has started.
From a high-level outsider perspective, the shift from 2.x to "current" looks like amateur hour.
You are hearing a lot of noise now, because 3.X has finally become viable enough to be interesting to the wider python community, I hope. That's why people keep hyping it.
3.0 was not ready, and only a few dedicated pythoneers (like Mark Pilgrim) pushed it.
It was very professional of the python community to keep 3.X in it's mother's basement until it was well-enough dressed to be seen in public.
From a high-level outsider perspective, the shift from 2.x to "current" looks like amateur hour.
I don't even know what this sentence means.
"Amateur hour" would be to expect the shift to occur overnight, with magic powers conferred by unicorns and butterflies. If you look at the developers posts (instead of random uninformed excitable blogs) you'll see that it was realistically expected to take a few years.
See, for instance, core developer J. Noller's comment here: http://news.ycombinator.com/item?id=2130854
I'm happy about PEP 380, it seems like they might as well do PEP 3152 as well since they're highly related...
But that would have been foolish of me: http://zope.stackless.com/Members/rmtew/News%20Archive/3.1.3
What would an "active" version of the project look like?
...
In other words, no one knows what you are talking about.