I'm really showing my ignorance now, I think; so, the old-style "fmt %
(tuple)" must use a different mechanism, and perhaps that's why np.savetxt
never choked on a float32 for me before (yes, I am on a 64-bit system).
In [8]: type(tmp.lat)
Out[8]: numpy.float32
In [9]: '%6s %8i %11.6f' % (tmp.
ZZ2001123 -23.82'
Thanks!
-Jon
On Jun 6, 2013, at 1:56 PM, Robert Kern wrote:
> On Thu, Jun 6, 2013 at 8:48 PM, Maccarthy, Jonathan K wrote:
>> Hi everyone,
>>
>> I've looked in the mailing list archives and with the googles, but haven't
>&
Hi everyone,
I've looked in the mailing list archives and with the googles, but haven't yet
found any hints with this question...
I have a float field in a NumPy record that looks like it's being substituted
as a string in the Python "{:f}".format() mini-language, thus throwing an error:
In [
