Jason Tackaberry wrote: > +TODO before 1.0: Yes!!!
> -Create doc in the Wiki and dump it into the doc subdir I started with it. Sadly, the Wiki has less doc than I remembered. > +- Eliminate explicit type() checking. Even isinstance() should be avoided > + where possible, relying instead of duck typing. I agree on the type stuff. But there are MANY type(s) and isinstance in the code. Why do you want to remove it? > +- Make sure SystemExit and KeyboardInterrupt is not silently caught. They > + should be bubbled up to the notifier loop. In other words, do not > + use catch-all except statements Agreed. I started with it some time ago. Are there still such cases in the code? > but rather 'except Exception' (which > + will not catch KeyboardInterrupt and SystemExit). IIRC KeyboardInterrupt is an Exception in 2.4 but not anymore in 2.5. So for 2.4 we need catch KeyboardInterrupt, SystemExit and raise it again and catch the rest after that. > +- Remove getters and setters (in the form get_foo() and set_foo()), using > + instead properties. This will result in significant API breakage, but > + is better to do that now than after 1.0 :) Yes > +- Rewrite of Process class Your job :) > +- Complete documentation Every help welcome > +TODO either before or after 1.0: > +- Unit testing suite (preferably before) I wanted it for a long time, but it is a huge task. Dischi -- Can I trade this job for what's behind door 1? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
