On Sat, Apr 16, 2011 at 12:02:57PM -0400, Chris Ball wrote:
> By the way, I see there are some new commits on one of the gitorious forks:
> 
> http://gitorious.org/~andrewcooper/be/andrewcooper-be/commits/master

I had been waiting for Andrew to address my response:

On Wed, Mar 30, 2011 at 05:04:52PM -0400, W. Trevor King wrote:
> 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.

But since it's been two weeks since last contact, I just went ahead
and made my proposed changes myself ;).

-- 
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

Attachment: pgps65PBTRwCb.pgp
Description: PGP signature

_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Reply via email to