Skip to content
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

Generation of python cache objects leaks host path on target #102

Open
ghost opened this issue Sep 1, 2023 · 0 comments
Open

Generation of python cache objects leaks host path on target #102

ghost opened this issue Sep 1, 2023 · 0 comments

Comments

@ghost
Copy link

ghost commented Sep 1, 2023

Hi!

When using genmsg / genpy to generate messages, the path of the host is leaked into the python cache modules. For example, in the official deployed ubunut packages, it is: for /opt/ros/noetic/lib/python3/dist-packages/std_msgs/__pycache__/__init__.cpython-38.pyc:

/tmp/binarydeb/ros-noetic-std-msgs-0.5.13/obj-x86_64-linux-gnu/devel/lib/python3/dist-packages/std_msgs/__init__.py

but it should be

/opt/ros/noetic/lib/python3/dist-packages/std_msgs/__init__.py

This is unwanted behavior. From the Docs, this path is used for

This [path] will appear in compilation time tracebacks, and is also compiled in to the byte-code file, where it will be used in tracebacks and other messages in cases where the source file does not exist at the time the byte-code file is executed.

Hence, the impact is very low, but still, it is an error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants