search

robotframework / OldSeleniumLibrary

Deprecated Selenium library for Robot Framework
Apache License 2.0
13 stars 3 forks source link

jybot: unicode errors in multiple places in the code #90

Closed spooning closed 9 years ago

spooning commented 9 years ago

Originally submitted to Google Code by bryan.oakley on 4 Feb 2010

With certain urls I'm getting the following error with Page Should Contain Element when the test is run with jybot:

UnicodeError: ascii encoding error: ordinal not in range(128)

I've attached a test file that duplicates the error (at least on my machine). All it takes is opening a browser to a document with unicode characters (eg: http://en.wikipedia.org/wiki/Pound_sterling) and running the keyword 'Page Should Contain Element' for an element not on the page. I suspect other keywords may exhibit the same problem.

Part of the problem is the debug statement in init.py, method _parse_locator. If I comment out the debug statement I get farther, but eventually it fails with the same error but somewhere else in the code.

I know there's a push to support Jython 2.5 but I really hope this gets fixed before then.

spooning commented 9 years ago

Originally submitted to Google Code by @yanne on 5 Feb 2010

Are you using Jython 2.2.1? Unicode in Jython 2.2.1 is totally broken, you should use Jython 2.2 with RF if you need unicode support.

With Jython 2.2 the attached example works.

spooning commented 9 years ago

Originally submitted to Google Code by bryan.oakley on 5 Feb 2010

interesting. Yes, we're using jython 2.2.1. Are there any downsides to regressing back to 2.2?

spooning commented 9 years ago

Originally submitted to Google Code by @yanne on 5 Feb 2010

From RF point of view no, we actually recommend to use Jython 2.2 with RF. Jython 2.2 has bugs in unicode handling also, but RF has workarounds for them.

spooning commented 9 years ago

Originally submitted to Google Code by @yanne on 8 Feb 2010

Closing this, since the cause is not library related.