-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add __init__.py to work around ansible-test/pylint bug #10926
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I thought sanity tests would complain about that.
I think they only complain if |
Backport to stable-10: 💚 backport PR created✅ Backport PR branch: Backported as #10927 🤖 @patchback |
@russoz thanks for reviewing! |
Add __init__.py to work around ansible-test/pylint bug. (cherry picked from commit 9dedd77)
Backport to stable-11: 💚 backport PR created✅ Backport PR branch: Backported as #10928 🤖 @patchback |
Add __init__.py to work around ansible-test/pylint bug. (cherry picked from commit 9dedd77)
…nd ansible-test/pylint bug (#10927) Add __init__.py to work around ansible-test/pylint bug (#10926) Add __init__.py to work around ansible-test/pylint bug. (cherry picked from commit 9dedd77) Co-authored-by: Felix Fontein <[email protected]>
…nd ansible-test/pylint bug (#10928) Add __init__.py to work around ansible-test/pylint bug (#10926) Add __init__.py to work around ansible-test/pylint bug. (cherry picked from commit 9dedd77) Co-authored-by: Felix Fontein <[email protected]>
SUMMARY
Ref: ansible/ansible#85990 (comment)
ISSUE TYPE
COMPONENT NAME
module utils