Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/004207.html below:

[Python-Dev] Towards native fileevents in Python (Was Re: Python multiplexing is too hard)

• Previous message: [Python-Dev] Towards native fileevents in Python (Was Re: Python multiplexing is too hard)
• Next message: [Python-Dev] Towards native fileevents in Python (Was Re: Python multiplexing is too hard)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ka-Ping Yee wrote:
> 
> On Tue, 23 May 2000, Alexandre Ferrieux wrote:
> >
> > Great !!! That's exactly the kind of Pythonic translation I was
> > expecting. Thanks !
> 
> Here's a straw man.  <watcher.py>

Nice. Now what's left to do is make select.select() truly
crossplatform...

> So is there no way to register more than one callback on a
> particular file?

Nope - it's considered the responsibility of higher layers.

> Do you ever find yourself wanting to do that?

Seldom, but it happened to me once, and I did exactly that: a layer
above.

-Alex

• Previous message: [Python-Dev] Towards native fileevents in Python (Was Re: Python multiplexing is too hard)
• Next message: [Python-Dev] Towards native fileevents in Python (Was Re: Python multiplexing is too hard)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4