Robert Bradshaw wrote: > That leaves (3), the > question of whether to allow any implicit string <--> char* > conversions (because it's so convenient, especially given the > ubiquitous nature of ASCII) or not (because if it's not explicit, > it's a bug).
Some more thoughts on that: Keeping unicode and bytes clearly separated makes good sense in py3, because you're in a high-level world that's firmly isolated from the outside. It's a viable strategy to convert all your data to unicode as soon as it comes in, and not have to worry about the issue otherwise. But the inside of a Pyrex module isn't such an isolated environment. At every turn, you're dealing with C code that doesn't make such a clear distinction between bytes and unicode. I'm not sure that trying to maintain the distinction rigidly for Python data, when there is all this C data around that doesn't maintain any such distinction, is worth the effort. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
