brett at python
Oct 26, 2009, 8:13 PM
Post #9 of 10
(779 views)
Permalink
|
On Mon, Oct 26, 2009 at 15:59, Steven D'Aprano <steve [at] pearwood> wrote:
> On Tue, 27 Oct 2009 08:54:52 am Nick Coghlan wrote:
> > Raymond Hettinger wrote:
> > > [GvR]
> > >
> > >> I still wish we could go back in time and unify sets and dicts, if
> > >> only to find out how that experiment would turn out.
> > >
> > > I'm curious about the outcome of another experiment along those
> > > lines. Is anyone seeing uptake for the set methods on mapping views
> > > in Py3.x?
> > >
> > > I haven't seen any code using it, nor any bug reports or
> > > documentation requests, nor any code in the ASPN cookbook, nor
> > > mention of it on the newsgroup or python-help.
> > >
> > > Has anyone here seen any hints about how this is faring in the
> > > wild?
> >
> > If anyone is looking for further explanation as to why Guido's
> > moratorium on core language changes is a good idea, allowing a chance
> > for answers to questions like Raymond's above a chance to evolve
> > naturally is what I see as the most important rationale.
>
> I don't understand that rationale. Let's take a concrete example. The
> new `yield from` syntax was accepted but now will be delayed by the
> moratorium. How would the addition of `yield from` delay or prevent
> people using set methods on mapping views?
>
>
It doesn't, but the point is we have already added several things to the
language in Python 3 that have gone mostly unused from the community thus
far. We do not need to continue to pile on the new features when we already
have a stack that we need to see if they pan out.
-Brett
|
