-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enable live patching of messages ? #12
Comments
I am not sure fit his is a mismatching features (using the namespace package of filefinder2), When a main package has a subpackage that is a namespace, does the |
Currently this is broken : tests in #13 We also need to test the namespace package case and compare py2 (filefinder2) and py3, and find out if it is because namespace packages or just a bug in our implementation... |
Actually not : fixing the dependent path makes it work : https://travis-ci.org/pyros-dev/rosimport/builds/271884845 |
But this works only because we "import" the generated class (which patches it) and then we instantiate that class when building the message. if neither the importing or the instantiation is done, then the patch will not be applied, which is logical. If we don't import the dependent message definition, the ros generated message code will do the import. but then it breaks:
There is probably a bug hiding around that corner... |
The current import system, when importing a message, looks for all its dependencies and generate ROS code for it.
This works fine, but it also means that a python code, cannot override or patch the generated ROS code.
It would be useful to be able to patch/extend a ROS message with some python code without modifying the generated code (usecase in pyros-msgs at the moment), at import time. But I am not sure it is even possible, while ROS message dependencies are other messages (directly, not the python source), and the python default import takes care of all cases (one cannot have an extension to python import system after FileFinder - currently, not a
.py
file will fail to import, without testing next importer in hooks).Anyway it might be something worth keeping in mind, although for now we ll implement some workaround in pyros-msgs.
The text was updated successfully, but these errors were encountered: