Closed potentialdiffer closed 3 years ago
Thanks for the report. It looks like it should be easy enough to use one of the other string methods for Dashing so that this doesn't happen. Would you mind opening a pull request to the dashing
branch fixing it?
This was fixed by #306, so closing.
Bug report
Required Info:
Steps to reproduce issue
Compiling package from source on systems with Python 3.5, e.g. Debian 9, Raspbian Stretch ...
Expected behavior
Successful compilation.
Actual behavior
Failing compilation due to syntax error caused by f-Strings.
Additional information
We experience compilation issues as of 01b55faf451c7af08b4aa60c7fcc7e1c2b206a4b with f-Strings which where introduced in Python 3.6 and are therefore not supported with earlier Python versions. [1] REP-2000 however states Python 3.5 as dashing's minimum requirements. [2]
A workaround is to fix the package to ros1_bridge version 0.7.6. Dashing support ends this May. I am not sure how relevant this is, but wanted to document it anyway.
[1] https://www.python.org/dev/peps/pep-0498/ [2] https://www.ros.org/reps/rep-2000.html#dashing-diademata-may-2019-may-2021