From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: python-inotify broken
Date: Sun, 19 Dec 2010 17:25:33 -0500 [thread overview]
Message-ID: <4D0E865D.8010002@balister.org> (raw)
In-Reply-To: <AANLkTiknCPruK-CPRKg7hkzhL02Byqk42Tur0a6_fu-7@mail.gmail.com>
On 12/19/2010 05:18 PM, AJ ONeal wrote:
> python-inotify, (bearing no relation to pyinotify or python-inotifyx, btw)
> is broken.
> it compiles, but it doesn't work.
>
> Can someone else confirm?
> test case:
> https://github.com/coolaj86/python-examples/tree/master/inotify
>
> After a few events it just freezes.
>
> I've also informed the author.
>
> Generally speaking, is there much point in leaving a library in OE that
> gives false
> hope and then shatters dreams and crushes aspirations?
Now you know it is broken, you should fix. Better for people to have a
place to start and not reinvent the wheel.
Deleting something just because it does not work is silly. Better to
figure out why and fix it.
Philip
next prev parent reply other threads:[~2010-12-19 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:18 python-inotify broken AJ ONeal
2010-12-19 22:25 ` Philip Balister [this message]
2010-12-20 0:49 ` AJ ONeal
2010-12-20 0:51 ` AJ ONeal
2010-12-20 1:31 ` AJ ONeal
2010-12-20 3:48 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0E865D.8010002@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox