unicode_new_subtype calls tp_alloc but passes in 0 for the size, so we can't use that. I'm attaching my latest work-in-progress patch for numpy, which mostly works (it has 3 remaining errors).ĪIUI, the "numpy.str_" type subclasses PyUnicodeObject but with its own custom allocator, which takes a size (this is called in PyArray_Scalar when type_num = NPY_UNICODE). Numpy pokes at the insides of PyUnicodeObject in a few places and is thus affected by the PEP 393 changes in Python 3.3 I've been trying to get numpy working with Python 3.3, and to so I had to make some changes to CPython - hence I'm posting this to the Python bug tracker. Hack-out-test-against-MAX_UNICODE-from-cpython-3.3.patchĭirty dirty hack applied to CPython 3.3. Work-in-progress patch for numpy to get it working with 3.3 Arfrever, alex, certik, dmalcolm, loewis, ncoghlan, pitrou, skrah, teoliphant, vstinnerĬreated on 21:10 by dmalcolm, last changed 15:59 by teoliphant.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |