On Nov 14, 2007 1:24 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Coincidentally, I just noticed this myself, and fixed it (and renamed it
> to is_writable_file_like). There will be (once I commit), and handful
> of places that use it.
By the way, your changes to make all the backends sup
John Hunter wrote:
>> At the same time, I notice that cbook.is_file_like is identical to
>> is_string_like. This seems worse than useless to me. If we are going
>> to have "is_file_like" then it should do something like check for read
>> and write methods.
>
> This looks like a bug. No other pa
On Nov 14, 2007 12:57 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> step_demo is failing because of this:
>
> In [4]:xx = numpy.ma.ones((2,3))
>
> In [5]:xx + ''
> Out[5]:array(NotImplemented)
>
A couple of days ago I was cleaning up references to Numeric and
numarray, and came across this
def is
step_demo is failing because of this:
In [4]:xx = numpy.ma.ones((2,3))
In [5]:xx + ''
Out[5]:array(NotImplemented)
which makes cbook.is_string_like(xx) return True. This is a pitfall of
duck-typing--sometimes something that quacks like duck is not a duck at all.
I can get back to this late
