Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #25006
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2012-07-07 01:29 -0700 |
| References | <456501fb-af2d-4741-9b73-33c65d7f0aa8@t1g2000pbl.googlegroups.com> <mailman.1884.1341646449.4697.python-list@python.org> |
| Subject | Re: why greenlet, gevent or the stackless are needed? |
| From | "self.python" <howmuchistoday@gmail.com> |
| Message-ID | <mailman.1885.1341649754.4697.python-list@python.org> (permalink) |
r
2012년 7월 7일 토요일 오후 4시 33분 26초 UTC+9, Devin Jeanpierre 님의 말:
> On Sat, Jul 7, 2012 at 3:09 AM, self.python <howmuchistoday@gmail.com> wrote:
> > it there somthing that "yield" can't do
> > or just it is easier or powerful?
>
> couroutine-like generators can't give up control flow unless they are
> the top level function handled by the coroutine controller thing. For
> example, we can do this:
>
> def foo():
> while True:
> next_value = (yield)
> print next_value
>
> But we can't do this:
>
> def yap():
> next_value = (yield)
> print next_value
>
> def foo():
> while True:
> yap()
>
> If we explicitly say that "yap" can control us, via "yield from" (new
> in Python 3.3), then we can do something like the above, but this
> still requires explicit markup. In all other releases of Python, this
> is impossible.
>
> On the other hand, coroutines in greenlet et al can do a coroutine
> context switch at any point. The upside is that this is more flexible
> (and does something generators pre-3.3 cannot). The downside is that
> you now need locking structures to guarantee atomic interactions with
> a shared resource, whereas with generators you know that you always
> are the sole thing running, until you do a yield (and unless real
> threads or greenlet or whatever are involved, of course.)
>
> -- Devin
first, thanks for good answer:)
but I don't understand why the code
def yap():
next_value = (yield)
print next_value
def foo():
while True:
yap()
really do.
what is the purpose of that code?
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
why greenlet, gevent or the stackless are needed? "self.python" <howmuchistoday@gmail.com> - 2012-07-07 00:09 -0700
Re: why greenlet, gevent or the stackless are needed? Devin Jeanpierre <jeanpierreda@gmail.com> - 2012-07-07 03:33 -0400
Re: why greenlet, gevent or the stackless are needed? "self.python" <howmuchistoday@gmail.com> - 2012-07-07 01:29 -0700
Re: why greenlet, gevent or the stackless are needed? "self.python" <howmuchistoday@gmail.com> - 2012-07-07 01:29 -0700
Re: why greenlet, gevent or the stackless are needed? Damjan <gdamjan@gmail.com> - 2012-07-07 17:38 +0200
csiph-web