Then what's this in RIDE?

I have version 1.2.0 of robotframework-Selenium2Library installed. I forked the project on GitHub and downloaded my fork onto my PC. I have NOT made any code changes, yet, to the downloaded Selenium2Library. I built on Win7 with Python 2.7 it by doing:
cd C:\_GIT_\robotframework-selenium2library
python setup.py install
When I add Selenium2Library into a test suite in RIDE, it finds this KW method (in C:\_GIT_\robotframework-selenium2library\src\Selenium2Library\keywords\_waiting.py) and displays its documentation:
def wait_until_element_is_visible(self, locator, timeout=None, error=None):
"""Waits until element specified with `locator` is visible.
Fails if `timeout` expires before the element is visible. See
`introduction` for more information about `timeout` and its
default value.
`error` can be used to override the default error message.
See also `Wait Until Page Contains`, `Wait Until Page Contains
Element`, `Wait For Condition` and BuiltIn keyword `Wait Until Keyword
Succeeds`.
"""
def check_visibility():
visible = self._is_visible(locator)
if visible:
return
elif visible is None:
return error or "Element locator '%s' did not match any elements after %s" % (locator, self._format_timeout(timeout))
else:
return error or "Element '%s' was not visible in %s" % (locator, self._format_timeout(timeout))
self._wait_until_no_error(timeout, check_visibility)
This raises 2 questions:
1. Why can’t this KW be found when running a test case with pybot?
2. Why does this method exist in this source file if it is NOT a KW method?
Thanks,
Martin
OOPS, I take it all back. This KW IS now visible and working when run with pybot. To get around some other issues I just upgraded my underlying Selenium to version 2.33 and now LOTS of stuff is working better!
Sorry for the trouble…
Martin
I’m not sure. I had several old versions of Selenium2Library installed, and an old version of the underlying Selenium library. I deleted them ALL from site-packages and then re-built Selenium2Library. It claimed to have installed its dependencies, but it didn’t and no Selenium was installed. The Library import showed red in RIDE. I had to manually install version 2.33 of Selenium for Python. Then it all started working.
Cheers,
Martin
From: Kevin O. [mailto:korm...@gmail.com]
Sent: Monday, June 24, 2013 12:35 PM
To: robotframe...@googlegroups.com
Cc: Taylor, Martin; jer...@gmail.com
Subject: Re: Keyword not found in Selenium2Library
I wrote that keyword. Hopefully we can add more of the waiting keywords Markus implemented in the Java port soon.