python-inotify broken

python-inotify broken

[AJ ONeal]

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?

AJ ONeal

Re: python-inotify broken

[Philip Balister]

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

Re: python-inotify broken

[AJ ONeal]

Maybe silly, maybe not. It takes just about as much time to learn a
library's internals as it does to write one.

Case and point: python-inotify.

If you google around for "python-inotify" you get the mainstream module that
Ubuntu and the rest of the Linux crowd are using.
This version of the same name has a different API, is a different package.

That's a bit confusing, don't you think?

In this particular case, it may be better to use one of the mainstream
inotify modules.
I can't even tell if this one is being actively maintained (though, like I
said, I e-mailed the author to find out).

That all said, I'm not a python developer, I don't want to figure it out. I
just want something to use.

AJ ONeal

On Sun, Dec 19, 2010 at 3:25 PM, Philip Balister <philip@balister.org>wrote:

> 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
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: python-inotify broken

[AJ ONeal]

I trailed off there...

Both points are valid:

Yours - better to fix what's broken then to create something new that adds
to the obscurity.
Mine - better to delete what's broken and create something new that works.

Reality - lot's of broken things everywhere, some of the same name.

On Sun, Dec 19, 2010 at 5:49 PM, AJ ONeal <coolaj86@gmail.com> wrote:

> Maybe silly, maybe not. It takes just about as much time to learn a
> library's internals as it does to write one.
>
> Case and point: python-inotify.
>
> If you google around for "python-inotify" you get the mainstream module
> that Ubuntu and the rest of the Linux crowd are using.
> This version of the same name has a different API, is a different package.
>
> That's a bit confusing, don't you think?
>
> In this particular case, it may be better to use one of the mainstream
> inotify modules.
> I can't even tell if this one is being actively maintained (though, like I
> said, I e-mailed the author to find out).
>
> That all said, I'm not a python developer, I don't want to figure it out. I
> just want something to use.
>
> AJ ONeal
>
>
> On Sun, Dec 19, 2010 at 3:25 PM, Philip Balister <philip@balister.org>wrote:
>
>> 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
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>

Re: python-inotify broken

[AJ ONeal]

The author just e-mailed me back. He is no longer maintaining the library.

I vote that it gets deleted unless whoever submitted it to OE plans to
maintain it.

It's just going to cause confusion for others like it did for me.
And going through all of the work to figure out how to access the
documentation just to find that it doesn't work for more than a minute...
frustrating.

AJ ONeal


On Sun, Dec 19, 2010 at 5:51 PM, AJ ONeal <coolaj86@gmail.com> wrote:

> I trailed off there...
>
> Both points are valid:
>
> Yours - better to fix what's broken then to create something new that adds
> to the obscurity.
> Mine - better to delete what's broken and create something new that works.
>
> Reality - lot's of broken things everywhere, some of the same name.
>
>
> On Sun, Dec 19, 2010 at 5:49 PM, AJ ONeal <coolaj86@gmail.com> wrote:
>
>> Maybe silly, maybe not. It takes just about as much time to learn a
>> library's internals as it does to write one.
>>
>> Case and point: python-inotify.
>>
>> If you google around for "python-inotify" you get the mainstream module
>> that Ubuntu and the rest of the Linux crowd are using.
>> This version of the same name has a different API, is a different package.
>>
>> That's a bit confusing, don't you think?
>>
>> In this particular case, it may be better to use one of the mainstream
>> inotify modules.
>> I can't even tell if this one is being actively maintained (though, like I
>> said, I e-mailed the author to find out).
>>
>> That all said, I'm not a python developer, I don't want to figure it out.
>> I just want something to use.
>>
>> AJ ONeal
>>
>>
>> On Sun, Dec 19, 2010 at 3:25 PM, Philip Balister <philip@balister.org>wrote:
>>
>>> 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
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>
>>
>

Re: python-inotify broken

[Khem Raj]

On (19/12/10 15:18), 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?

hmmm well its there, it may not be in best shape but I guess you get a
starting point. here is your opportunity I guess you have to debug it and fix it if possible and
contribute to OE
someone who is stuck in same situation as you can help.

-Khem