Re: Why are "broken iterators" broken?

Discussion in 'Python' started by Fredrik Lundh, Sep 22, 2008.

  1. Cameron Simpson wrote:

    >> you probably want the consumer thread to block when it catches up with
    >> the producer, rather than exit.

    >
    > It sounds like he wants non-blocking behaviour in his consumer.


    Roy gave an example, he didn't post a requirements specification.

    > A common example is "try to gather a lot of stuff into a single packet,
    > but send a smaller packet promptly if there isn't much stuff".


    that use case is better solved with a plain list object. no need to
    make things harder than they are.

    </F>
    Fredrik Lundh, Sep 22, 2008
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. =?Utf-8?B?VGltOjouLg==?=

    Why, why, why???

    =?Utf-8?B?VGltOjouLg==?=, Jan 27, 2005, in forum: ASP .Net
    Replies:
    6
    Views:
    563
    Juan T. Llibre
    Jan 27, 2005
  2. Mr. SweatyFinger

    why why why why why

    Mr. SweatyFinger, Nov 28, 2006, in forum: ASP .Net
    Replies:
    4
    Views:
    875
    Mark Rae
    Dec 21, 2006
  3. Mr. SweatyFinger
    Replies:
    2
    Views:
    1,804
    Smokey Grindel
    Dec 2, 2006
  4. Steven D'Aprano

    Why are "broken iterators" broken?

    Steven D'Aprano, Sep 21, 2008, in forum: Python
    Replies:
    8
    Views:
    645
  5. Cameron Simpson

    Re: Why are "broken iterators" broken?

    Cameron Simpson, Sep 22, 2008, in forum: Python
    Replies:
    0
    Views:
    580
    Cameron Simpson
    Sep 22, 2008
Loading...

Share This Page