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

Use an explicit relative import path instead of implicit. #471

Merged
merged 1 commit into from
Aug 17, 2020

Conversation

fmauch
Copy link
Contributor

@fmauch fmauch commented Aug 10, 2020

On python3 systems the implicit relative import will not work. The explicit
notation, however, should work on python >= 2.5

I am targeting melodic, as I myself am using ROS melodic with a python3 environment. According to REP-0003 noetic-devel would probably be a more appropriate target branch, but it probably wouldn't hurt to include it into melodic, as well.

On python3 system the implicit relative import will not work. The explicit
notation, however, should work on python >= 2.5
@bmagyar bmagyar merged commit e1ef19a into ros-controls:melodic-devel Aug 17, 2020
bmagyar pushed a commit that referenced this pull request Aug 17, 2020
On python3 system the implicit relative import will not work. The explicit
notation, however, should work on python >= 2.5
@bmagyar
Copy link
Member

bmagyar commented Aug 17, 2020

I've cherry-picked to noetic too and pushing a new release to both noetic and melodic with this, thanks for the contribution!

@fmauch fmauch deleted the fix_import branch August 25, 2020 09:50
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 this pull request may close these issues.

None yet

2 participants