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

Fix warnings when using mypy 1.8.0. #89

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

clalancette
Copy link
Contributor

For reasons I admit I don't understand, when using mypy 1.8.0 with this code it fails to determine that it can import submodules from launch properly. Since we can easily workaround this by just doing 'import launch', do that here.

For reasons I admit I don't understand, when using mypy
1.8.0 with this code it fails to determine that it
can import submodules from launch properly.  Since we
can easily workaround this by just doing 'import launch',
do that here.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
Copy link
Member

@christophebedard christophebedard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I've come across these errors (or similar ones) before in #27. It might be due to the [no-]implicit-reexport flag: https://mypy.readthedocs.io/en/stable/command_line.html#cmdoption-mypy-no-implicit-reexport. So it might not like imports of an implicitly-reexported value even though it works in practice.

Nevertheless, this is fine.

@clalancette
Copy link
Contributor Author

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

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.

2 participants