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
TST: add future unicode_literals test (#786) #790
Conversation
I'm not quite sure if this is reliably cross-platform. On Windows, Also, we're aiming for Python 3 compatibility for 0.12, so we need to be careful with this test. We probably need to add a |
check using isinstance instead for the length of the string
Ok, I used |
Great, thanks, that's definitely neater. In fact, I think it would now pass after conversion to Python 3, but I'll probably add a decorator to skip it anyway. One minor niggle: the second argument to assert isinstance(ip.user_ns['unicode_str'], unicode), 'strings literals are not being interpreted as unicode' |
remove ambiguous assert messages for unicode_literals test
ok, you're right about the assert message. Since I find it a bit awkward, I remove them altogether. |
TST: add future unicode_literals test (#786)
Excellent. Thanks, Olivier - it's merged. |
check using isinstance instead for the length of the string
remove ambiguous assert messages for unicode_literals test
TST: add future unicode_literals test (ipython#786)
add simple test to check that the bug #786 is indeed fixed in master