Merged. Thanks again for the input!
I will look into the unicode issue and respond on the other thread.
-John
On Sat, Mar 15, 2014 at 7:50 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Fri, Mar 14, 2014 at 9:04 PM, John Chilton jmchil...@gmail.com wrote:
On Fri, Mar 14, 2014 at 10:24 AM,
On Fri, Mar 14, 2014 at 9:04 PM, John Chilton jmchil...@gmail.com wrote:
On Fri, Mar 14, 2014 at 10:24 AM, Peter Cock p.j.a.c...@googlemail.com
wrote:
Thanks John,
I suggest making this test framework perform this check by default
(the twill and API based frameworks) and seeing what - if
On Sat, Mar 15, 2014 at 12:50 PM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Fri, Mar 14, 2014 at 9:04 PM, John Chilton jmchil...@gmail.com wrote:
On Fri, Mar 14, 2014 at 10:24 AM, Peter Cock p.j.a.c...@googlemail.com
wrote:
Thanks John,
I suggest making this test framework perform this
Thanks John,
I suggest making this test framework perform this check by default
(the twill and API based frameworks) and seeing what - if anything -
breaks as a result on the Test Tool Shed.
Note that one area of fuzziness is subclasses, e.g. if the tool output
was labelled fastqsanger, but the
On Fri, Mar 14, 2014 at 10:24 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
Thanks John,
I suggest making this test framework perform this check by default
(the twill and API based frameworks) and seeing what - if anything -
breaks as a result on the Test Tool Shed.
Hey Peter,
I hope it