Python version of the remote server should support also dynamic libraries #187
Comments
Does it support dynamic library APIs now? It's import to us. |
No, the dynamic library API is not supported currently. If it was, this issue wouldn't be open. If you happen to work for NSN you can contact the core team via internal mailing lists and we can probably include this support into the scope of RF 2.6. If you don't work for NSN, then you need to implement this support yourself or pay someone to do it for you. |
Yeah. I implemented it. It is still a problem for same name keywords if loaded all libraries. |
Python remote server has moved to separate project. And so has this issue: |
Marking as invalid in this issue tracker. |
Currently the Python version of the remote server (see issue 118 for more
information about Remote library and associated servers) can wrap "normal"
libraries using the static and the dynamic library API, but it should also
support the dynamic API.
This functionality is easiest tested with unit tests in
test_remoteserver.py. I created this file when I added support for hybrid
libraries ( issue 180 ).
The text was updated successfully, but these errors were encountered: