<br><br><div class="gmail_quote">On Sat, May 23, 2009 at 6:37 PM, Eric Firing <span dir="ltr"><<a href="mailto:efiring@hawaii.edu">efiring@hawaii.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Charles R Harris wrote:<br>
><br>
><br>
> On Sat, May 23, 2009 at 6:03 PM, Robert Kern <<a href="mailto:robert.kern@gmail.com">robert.kern@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:robert.kern@gmail.com">robert.kern@gmail.com</a>>> wrote:<br>
><br>
> On Sat, May 23, 2009 at 18:57, Charles R Harris<br>
</div><div class="im">> <<a href="mailto:charlesr.harris@gmail.com">charlesr.harris@gmail.com</a> <mailto:<a href="mailto:charlesr.harris@gmail.com">charlesr.harris@gmail.com</a>>> wrote:<br>
> > You were supposed to be able to change the default behaviour, but<br>
> it didn't<br>
> > used to work. I think if you are going to use a warning as a flag<br>
> then it<br>
> > has to always be raised when a failure occurs, not just the first<br>
> time.<br>
><br>
> A brief test suggest that in Python 2.5.4, at least, as long as you<br>
> set the action to be 'always' before the warning is first issued, it<br>
> works. We can do this just after the IOWarning (or whatever) gets<br>
> defined.<br>
><br>
><br>
> OK, that would work. Although I think a named argument might be a more<br>
> transparent way to specify behaviour than setting the warnings.<br>
<br>
</div>I agree; using a warning strikes me as an abuse of the warnings<br>
mechanism. Instead of a "strict" flag, which I find not particularly<br>
expressive--what is it being "strict" about?--how about a "min_count"<br>
kwarg to go with the existing "count" kwarg?<br>
</blockquote><div><br>I didn't like the fact that it overlaps with count. Although I suppose it could be the minimum and count the maximum if we enforce min_count <= count. But that still seems a bit clumsy.<br><br>
Chuck<br><br></div></div><br>