-
Notifications
You must be signed in to change notification settings - Fork 758
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
Incompatibility with forthcoming RF 2.9 alpha 3 #429
Comments
Notice that our plan is to get RF 2.9a3 released already tomorrow. I doubt a new Se2Lib version can be released before that. One possibility is that we add |
Um, I can do a minor update with just that in it if you consider it really critical. |
@pekkaklarck, No changes have went in since the 1.7.0 release, I'm more than willing to push out 1.7.1 with just this in it. Would that be acceptable to you? |
I added GLOBAL_VARIABLES to robot.variables for backwards compatibility. robotframework/robotframework@75568dd We would like to remove this in future, so a new release sooner rather than later would still be great. |
I think a 1.7.1 release would be justified. |
1.7.1 release would be great but now that we added |
Well, I've already made the necessary changes. It wasn't actually listed in many places. I've got other things planned, but there isn't any substantial changes planned until the next major release. 1.7.* stuff from here on in will be mostly documentation and test updates. |
This is fixed as of #431. I just need to bump the release which I can do in a few hours. |
If creating 1.7.1 is not much work, getting it out ASAP would be awesome. We'll still keep |
I'm working on it now. Having some difficulties with the build process though, I'll get back with you soon. |
@pekkaklarck, It's done now. Sorry it took so long, I've been busy with work. |
Dear all, in 2.9b2 for the following setup I would like to report the following error: A. OS: Windows version 7 On iPython, on importing Page, I get the following error: In [1]: from robotpageobjects import Page C:\Users\rramasubramanian\AppData\Local\Continuum\Anaconda\envs\rf29a3\lib\site-packages\robotpageobjects\context.py in () ImportError: cannot import name init_global_variables |
@rama-bornfree, that seems to be a problem with robotframework-pageobjects. As you can see above, I submitted an issue about RF 2.9 compatibility to its tracker. |
Ha, @pekkaklarck, you beat me to it. |
@pekka and @ Zephraph, thank you very much for the findings on PO, i will On Monday, July 6, 2015, Zephraph notifications@github.com wrote:
|
The issue occurs for selenium RC1 library v2.9.1: |
@vikulin, you need to update S2L. |
You are @vikulin still using the old SeleniumLibrary, right? I highly recommend switching to Selenium2Library, but I guess we need to fix this incompatibility in the old and deprecated library too. Issues related to it should be submitted to its tracker, though. |
Sent issue to the tracker https://code.google.com/p/robotframework-seleniumlibrary/issues/detail?id=273 |
zephraph, S2L update is not an easy task. All RC1 keywords are not compatible with S2L. |
Sorry, I looked over the RC1 part. I don't have any involvement in that project so I won't be any help. |
zephraph, I'm not asking you any help. |
Guys, any updates? |
@alexeylubyanoy, recent versions of S2L? |
@zephraph, sorry - I was sure I am posting this to android library repository |
Haha, no problem. |
Hi all! I still have this problem
This is pip freeze
|
Your version of Selenium2Library is not compatible with the Robot Framework. This issue is fixed from version 1.7.1 onwards. |
Thank you so much.
Could you possibly create requirements.pip? |
There are requirements for pip, but we want and we are keep our backwards compatibility. And therefore the requirements are quite low. But there are few these kind of situations which causes a problem and those could be documented better. If you feel that this is a problem, please raise an separate issue for it. |
That I get this exception when using Selenium2Library with the latest Robot Framework code:
Apparently the library uses Robot's internal
GLOBAL_VARIABLES
that we just we able to remove as part of robotframework/robotframework#532. I don't have time to investigate where and whyGLOBAL_VARIABLES
are used right now, but I hope the usage could be replaced with something else. I would assume variable related methods inBuiltIn
could be used instead. A big benefit of them is that they are part of the public API and thus considered stable.If it turns out to be hard to fix this on Se2Lib, we can consider adding
GLOBAL_VARIABLES
back for some time. Our general goal is to get rid of all/most global state like that to make the framework thread safe and easier to parallelize, though.The text was updated successfully, but these errors were encountered: