8000 Support for dynamic library API · Issue #18 · robotframework/PythonRemoteServer · GitHub
[go: up one dir, main page]
Skip to content

Support for dynamic library API #18

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.

Sign up for GitHub

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

Jump to bottom
Closed
pekkaklarck opened this issue Mar 18, 2014 · 3 comments
Closed

Support for dynamic library API #18

pekkaklarck opened this issue Mar 18, 2014 · 3 comments
Assignees
@pekkaklarck
Labels
enhancement prio-critical
Milestone
v1.1

Comments

@pekkaklarck
Copy link
Member

Currently the remote server supports only static and hybrid APIs. Supporting also the dynamic API shouldn't be too complicated and would mean all library APIs are covered.

There exits an old pull request #1 that implements this functionality. Unfortunately changes done in 1.0 version mean that it cannot be anymore cleanly merged. I also have quite big refactoring plans for the code in general, and the approach in the pull request isn't compatible with them.
@pekkaklarck pekkaklarck mentioned this issue Mar 18, 2014
Closed
@pekkaklarck pekkaklarck added this to the 1.1 milestone Mar 18, 2014
@spooning spooning mentioned this issue Jun 29, 2014
Closed
@rainmanwy
Copy link

Hi, Pekka

How about this issue, do you have plan to implement it?
i found "get_keyword_arguments" and "get_keyword_documentation" do not support dynamic libraries.

I am trying to implement a libraries which will expose some classes(Some protocols such as IP, TCP, ICMP which are implemented as python classes) as keywords to robot framework.

I have tried hybrid mode, these classes could not be imported as keywords as RF will check the type.

so i implement it as dynamic libraries, but it could not work with this remote server.

Do you have any suggestions about this?

@pekkaklarck
Copy link
Member Author

So far this hasn't been important enough for anyone to provide a new PR or pay me or someone to implement it.

@pekkaklarck pekkaklarck modified the milestones: 1.2, 1.1 Jan 9, 2017
@pekkaklarck pekkaklarck self-assigned this Jan 10, 2017
@pekkaklarck
Copy link
Member Author

Did some refactoring to the code and one of the benefits was that adding dynamic library support became easier. I already got it mostly done.

pekkaklarck added a commit that referenced this issue Jan 10, 2017
@pekkaklarck
Dynamic library support #18
a9b6ff3 
Still need to add some acceptance tests.
pekkaklarck added a commit that referenced this issue Jan 10, 2017
@pekkaklarck
Acceptance tests for dynamic library support. #18
7e27df7 
Also a fix for a bug found by the tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pekkaklarck pekkaklarck

Labels
enhancement prio-critical
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
2 participants
@pekkaklarck @rainmanwy
0