On Apr 17, 2016 10:47 AM, "Olivier Grisel" <olivier.gri...@ensta.org> wrote: > > Thanks for the clarification, I read your original report too quickly. > > I wonder why the travis maintainers built Python 2.7 with a > non-standard unicode option.
Because for some reason cpython's configure script (in the now somewhat ancient versions we're talking about) defaults to non-standard broken Unicode support, and you have to explicitly override it if you want working standard Unicode support. I guess this made sense in like the 90s before people realized how unicode was going to go down. Same issue affects pyenv users (or used to, I think they might have just fixed it [0]) and Enthought Canopy. -n [0] https://github.com/yyuu/pyenv/issues/257
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
