-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle unicode better #158
Comments
related to #138 I'm struggling to figure out how this actually works. It seems that casa has its own string type implementation. For python3 when a string is encoded it becomes a byte string type, while for python2 it is still a string. I feel that is is going to be painful. |
i guess this is causing the problems for py3 |
merged! |
python-casacore often doesn't handle unicode strings properly, giving errors like this:
The text was updated successfully, but these errors were encountered: