Hi and thanks Trevor I didn't get your reply. Maybe it was "captured" in my spam-filter.
When I look in the values files they seem to be binary summary: !!binary | Rml4YSBz5SBhdHQgbWFuIGthbiBza2FsYSB2YXJpYWJsZXIgaSBTY2lsYWIgaXN05GxsZXQgZvZy IGF0dCBhbnbkbmRhIGxvZ3Rvb2w= Any ideas what to do? Best regards Anders 2011/3/30 W. Trevor King <[email protected]> > On Tue, Mar 29, 2011 at 07:04:26PM +0000, Andrew Cooper wrote: > > My question is, how do I add tests for the new options? > > Currently the simplest approach is to add them to the class doctest. > If the doctest interface is too awkward, you can use unit tests hidden > inside an `if libbe.TESTING == True` block at the end of the module. > See libbe.bugdir for details. > > Looking at your patches, I think the assigned processing in > be713557650 should be split out as a stand-alone function > libbe.command.assign.parse_assigned(string) > which could then be used in both Assign, New, and potentially other > command classes (where appropriate). This would ensure a consistent > interface across all commands. > > > Also, how should I send the patches when they are complete? > > It looks like you have a branch on Gitorious already. Just email this > list when things are ready to merge, and we can pull from there. > > Cheers, > Trevor > > -- > This email may be signed or encrypted with GPG (http://www.gnupg.org). > The GPG signature (if present) will be attached as 'signature.asc'. > For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy > > My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt > > _______________________________________________ > Be-devel mailing list > [email protected] > http://void.printf.net/cgi-bin/mailman/listinfo/be-devel > >
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
