On Fri, Jul 18, 2014 at 9:07 AM, Pauli Virtanen <p...@iki.fi> wrote: > Another approach would be to add a new 1-byte unicode
you can't do unicode in 1-byte -- so what does this mean, exactly? > This also is not perfect, since array(['foo']) on Py2 should for > backward compatibility continue returning dtype='S'. yup. but we may be OK -- as "bytes" in py2 is the same as string anyway. But what do we do with null bytes? when going from 'S' to py2 string? -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
