isgenerator(...) - anywhere to be found?

Jean-Paul Calderone exarkun at divmod.com
Tue Jan 22 09:34:33 EST 2008


On Tue, 22 Jan 2008 15:15:43 +0100, "Diez B. Roggisch" <deets at nospam.web.de> wrote:
>Jean-Paul Calderone wrote:
>
>> On Tue, 22 Jan 2008 14:20:35 +0100, "Diez B. Roggisch"
>> <deets at nospam.web.de> wrote:
>>>For a simple greenlet/tasklet/microthreading experiment I found myself in
>>>the need to ask the question
>>>
>>> [snip]
>>
>> Why do you need a special case for generators?  If you just pass the
>> object in question to iter(), instead, then you'll either get back
>> something that you can iterate over, or you'll get an exception for
>> things that aren't iterable.
>
>Because - as I said - I'm working on a micro-thread thingy, where the
>scheduler needs to push returned generators to a stack and execute them.
>Using send(), which rules out iter() anyway.

Sorry, I still don't understand.  Why is a generator different from any
other iterator?

Jean-Paul



More information about the Python-list mailing list