First summary:

I will do the following tomorrow. All API changes will be written down
in base/API_CHANGE.txt.

1. Adjust all kaa modules and freevo to the new notifier namespace
   stuff. The deprecated warnings in kaa.base will be kept but should
   not be visible for any kaa modules and Freevo 2.0. But since we
   break the API, they will be removed before the next release.

2. Rename ThreadCallback to NamedThreadCallback and adjust all the
   code.

3. Rename Thread to ThreadCallback and rename start to __call__. A new
   Thread class will inherit from ThreadCallback and add a deprected
   warning and this functions also has a start function with a
   deprected warning.

4. Adjust all kaa modules and Freevo to the new thread naming

5. Include BackgroundTask. That should work without breaking the API
   but I will check.

6. Add support for foo = yield something in kaa.base. This will
   require some Python 2.4/2.5 checking because I'm not sure if Freevo
   1.8 is not using kaa.rpc which uses the decorator stuff. All code
   in kaa.base will use the old style code to get the yield
   results. The same will be true for kaa.imlib2 and kaa.metadata but
   I guess they don't use it.

That will be the first part of the API change. I will check this with
Python 2.4 and 2.5. All tests in kaa.base should work with both python
versions.

If I have some time I will start making beacon depend on 2.5 which
means I will use the new decorator style code for testing. This means
kaa.base, kaa.imlib2 and kaa.metadata should work with Python 2.4, all
other modules may use the new yield style and also add some additional
Python 2.5 code like with-statements and relative imports.


Is that ok with everyone?


Dischi

-- 
Black holes suck.

Attachment: pgpLGXwJIvxIB.pgp
Description: PGP signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to