Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Christoph Gohlke
On 7/28/2012 6:17 PM, Christoph Gohlke wrote: > On 7/28/2012 6:09 PM, Ondřej Čertík wrote: >> On Sat, Jul 28, 2012 at 5:09 PM, Ondřej Čertík >> wrote: >>> On Sat, Jul 28, 2012 at 3:31 PM, Ondřej Čertík >>> wrote: On Sat, Jul 28, 2012 at 3:04 PM, Ondřej Čertík wrote: > Many of th

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Christoph Gohlke
On 7/28/2012 6:09 PM, Ondřej Čertík wrote: > On Sat, Jul 28, 2012 at 5:09 PM, Ondřej Čertík > wrote: >> On Sat, Jul 28, 2012 at 3:31 PM, Ondřej Čertík >> wrote: >>> On Sat, Jul 28, 2012 at 3:04 PM, Ondřej Čertík >>> wrote: Many of the failures in https://gist.github.com/3194707/5696

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 5:09 PM, Ondřej Čertík wrote: > On Sat, Jul 28, 2012 at 3:31 PM, Ondřej Čertík > wrote: >> On Sat, Jul 28, 2012 at 3:04 PM, Ondřej Čertík >> wrote: >>> Many of the failures in >>> https://gist.github.com/3194707/5696c8d3091b16ba8a9f00a921d512ed02e94d71 >>> are of the ty

[Numpy-discussion] ANN: pythonpackages.com beta

2012-07-28 Thread Alex Clark
Hi NumPy folks, I am reaching out to various Python-related programming communities in order to offer new help packaging your software. If you have ever struggled with packaging and releasing Python software (e.g. to PyPI), please check out this service: - http://pythonpackages.com The bas

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 3:31 PM, Ondřej Čertík wrote: > On Sat, Jul 28, 2012 at 3:04 PM, Ondřej Čertík > wrote: >> Many of the failures in >> https://gist.github.com/3194707/5696c8d3091b16ba8a9f00a921d512ed02e94d71 >> are of the type: >> >> ===

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 3:04 PM, Ondřej Čertík wrote: > Many of the failures in > https://gist.github.com/3194707/5696c8d3091b16ba8a9f00a921d512ed02e94d71 > are of the type: > > == > FAIL: Check byteorder of single-dimensional obj

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
Many of the failures in https://gist.github.com/3194707/5696c8d3091b16ba8a9f00a921d512ed02e94d71 are of the type: == FAIL: Check byteorder of single-dimensional objects -

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 11:19 AM, Stefan Krah wrote: > Ond??ej ??ert??k wrote: >> So at some point, the strings get converted to numpy strings in 3.2, >> but not in 3.3. > > PyArray_Scalar() must return a subtype of PyUnicodeObject. I'm boldly > assuming that data is in utf-32. If so, then this u

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Stefan Krah
Ond??ej ??ert??k wrote: > So at some point, the strings get converted to numpy strings in 3.2, > but not in 3.3. PyArray_Scalar() must return a subtype of PyUnicodeObject. I'm boldly assuming that data is in utf-32. If so, then this unoptimized version should work: diff --git a/numpy/core/src/mu

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 8:04 AM, Ondřej Čertík wrote: > On Sat, Jul 28, 2012 at 7:58 AM, Ondřej Čertík > wrote: > [...] >> Here is the code in defchararray.py: >> >> >> 1911if not _globalvar and self.dtype.char not in 'SUbc': >> 1912raise ValueError("Can only create a

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
On Sat, Jul 28, 2012 at 7:58 AM, Ondřej Čertík wrote: [...] > Here is the code in defchararray.py: > > > 1911if not _globalvar and self.dtype.char not in 'SUbc': > 1912raise ValueError("Can only create a chararray from > string data.") > 1913 > 1914def __getitem

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Ondřej Čertík
Stefan, On Sat, Jul 28, 2012 at 2:36 AM, Stefan Krah wrote: > Ond??ej ??ert??k wrote: >> >> I took a brief look at it, and from the errors I have seen, one is >> >> cosmetic, the other one is a bit more involved (rewriting >> >> PyArray_Scalar unicode support). While it is not difficult in natur

Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-07-28 Thread Stefan Krah
Ond??ej ??ert??k wrote: > >> I took a brief look at it, and from the errors I have seen, one is > >> cosmetic, the other one is a bit more involved (rewriting > >> PyArray_Scalar unicode support). While it is not difficult in nature, > >> the current code has multiple #ifdef of Py_UNICODE_WIDE, me