On Sat, Aug 4, 2012 at 12:58 PM, Stefan Krah wrote:
> Nathaniel Smith wrote:
>> On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah
>> wrote:
>> > switch (descr->byteorder) {
>> > case '<':
>> > byteorder = -1;
>> > case '>':
>> > byteorder = 1;
>> >
Nathaniel Smith wrote:
> On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah
> wrote:
> > switch (descr->byteorder) {
> > case '<':
> > byteorder = -1;
> > case '>':
> > byteorder = 1;
> > default: /* '=', '|' */
> > byteorder = 0;
> >
On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah wrote:
> switch (descr->byteorder) {
> case '<':
> byteorder = -1;
> case '>':
> byteorder = 1;
> default: /* '=', '|' */
> byteorder = 0;
> }
I think you might want some break
Travis Oliphant wrote:
> The difficulty starts when you start to interact with the unicode array
> scalar (which is the same data-structure exactly as a Python unicode object
> with a different type-name --- numpy.unicode_).However, I overlooked the
> "encoding" argument to the standard "un
On Fri, Aug 3, 2012 at 6:03 PM, Travis Oliphant wrote:
> Hey all,
>
> Ondrej has been working hard with feedback from many others on improving
> Unicode support in NumPy (especially for Python 3.3). Looking at what
> Python has done in Python 3.3 (PEP 393) and chatting on the Python issue
> t
On Fri, Aug 3, 2012 at 7:03 PM, Travis Oliphant wrote:
> Hey all,
>
> Ondrej has been working hard with feedback from many others on improving
> Unicode support in NumPy (especially for Python 3.3). Looking at what
> Python has done in Python 3.3 (PEP 393) and chatting on the Python issue
> tra
