Re: kaa.metadata starts kaa main loop?

Hi

On 09.08.2010 01:05, Jason Tackaberry wrote:
> I'm not aware of anything in kaa.metadata that depends on the mainloop.
> I consider your problem to be a bug in kaa.base.

Agreed. kaa.base is needed for some stuff, but not the mainloop

> I do see code in kaa.base that adds handlers to SIGTERM and SIGINT when
> kaa.main is imported.  This seems like a bad idea to me.

It is needed for a clean mainloop shutdown

> dischi, this looks like your code, so I don't want to change anything
> before double checking.  I think we should do this the first time
> kaa.main.loop() is called, and only replace default handlers, not
> handlers that might have been previously set by the user.  Objections if
> I make this change?

No, sounds good to me

> We need to continue to minimize the amount of stuff we do at import
> time.

Yes

>> Also, what's the point on having a metadata library if it depends so
>> heavily on kaa as a whole?
> 
> kaa.metadata depends only on kaa.base for some helper functions and
> distutils stuff.  All kaa modules depend on kaa.base.
> 
> But kaa.metadata doesn't presently depend on the kaa mainloop, so it
> should be perfectly usable for what you're trying to do.  The fact that
> it isn't is a bug.

Yes

Dischi

-- 
"I don't suffer from insanity. I enjoy every minute of it."

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev