Lisandro Dalcin wrote: > Stefan, in this commit > > changeset: 1743:58406a9db77b > user: Stefan Behnel <[email protected]> > date: Sat Feb 21 21:08:46 2009 +0100 > summary: unicode fixes for numpy test (untested, hopefully not > breaking everything) > > your broke everything ;-)
Sorry 'bout that! :) I fixed that, changing the NumPy parameters from u'...' to b'...' should make it work. I'll push it as soon as I get the conflict resolved that I just got from you. :o) > BTW, I still want Cython to let me specify in an easy way that a > string literal should match the one Python normally uses for > identifier... > > For example: > > np.arange(10, dtype=s'i') > > Then s'i' literal whould be PyString in Py2 and PyUnicode in Py3... However, that makes it sound like it's NumPy that's broken here. There's absolutely no reason why the parameters should be byte strings. I still doubt that such a feature is really needed. Any API that requires byte strings where unicode strings would be appropriate is broken. The above will become useless (and even semantically wrong) once NumPy is fixed. Other libraries that currently require this will also be fixed in the not so far future. > Stefan, we really need this... IMHO this is a clear case where > practicality beats purity.... Is NumPy actually Py3 compatible? If not, it's definitely not a case for a decision either way. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
