In article <04180ce5-4cc0-43a4-b26a-b7a4fe826...@g23g2000yqh.googlegroups.com>,
IngoognI wrote:
>On Sep 8, 6:19=A0am, a...@pythoncraft.com (Aahz) wrote:
>>
>> There's no direct equivalent to Linux inotify [...]
>
>pnotify ?
Thanks! I'll look into that.
--
Aahz (a...@pythoncraft.com)
On Sep 8, 6:19 am, a...@pythoncraft.com (Aahz) wrote:
> There's no direct equivalent to Linux inotify [...]
pnotify ?
ingo
--
http://mail.python.org/mailman/listinfo/python-list
In article ,
wrote:
>On 12:57 am, a...@pythoncraft.com wrote:
>>In article >46f3-9a03-46f7125f5...@r5g2000yqi.googlegroups.com>,
>>Nicolas Dumazet wrote:
>>>
>>>kqueue has the limitation that kern.kq_calloutmax is usually set
>>>at 4096. Meaning that one could not use this on a big (Mercurial)
On 12:57 am, a...@pythoncraft.com wrote:
In article 46f3-9a03-46f7125f5...@r5g2000yqi.googlegroups.com>,
Nicolas Dumazet wrote:
On Sep 3, 10:33=A0pm, a...@pythoncraft.com (Aahz) wrote:
I'm curious why you went with FSEvents rather than kqueue. My company
discovered that FSEvents is rather co
In article ,
Nicolas Dumazet wrote:
>On Sep 3, 10:33=A0pm, a...@pythoncraft.com (Aahz) wrote:
>>
>> I'm curious why you went with FSEvents rather than kqueue. My company
>> discovered that FSEvents is rather coarse-grained: it only tells you that
>> there has been an event within a directory, it
On Sep 3, 10:33 pm, a...@pythoncraft.com (Aahz) wrote:
> I'm curious why you went with FSEvents rather than kqueue. My company
> discovered that FSEvents is rather coarse-grained: it only tells you that
> there has been an event within a directory, it does *not* tell you
> anything about the chang
[posted to c.l.py with cc in e-mail, reply to group preferred]
In article ,
Nicolas Dumazet wrote:
>
>I am proud to announce the first release of pyfsevents, a C extension
>providing a Python interface to the FSEvents API.
>FSEvents is an Apple framework for Mac OS X >=3
