-
Notifications
You must be signed in to change notification settings - Fork 27
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
set zip_safe to avoid warning during installation #29
Conversation
Thanks these warnings were one on the only thing polluting stderr during builds. |
When the flag is not specified the warning indicates what is being chosen based on the package content (e.g. usage of |
Looking at the nightlies, packages in other repositories (ros2cli or examples) produce similar console pollution, but they are not covered by this set of PRs. So the question of how the packages targeted by this set of PRs were chosen still stands. I'm fine merging those without review as without a job confirming the disappearance of the warnings or a summary of the console outputs that motivated this change; it is hard to review as it forces the reviewer to go dig them out from previous jobs output and compare the flag with what is set in this set of PRs. |
There is always more to fix. I addressed the ones I notices. I won't spend time right now looking for more of these. But whenever I stumble over additional warnings in the future (as with any other problem) I will create more PRs. Please feel free to run CI if you think it help in the review process. I don't think it will have any effect on passing / failing the build or the test results. |
I opened the missing PRs as it made it easier to review the existing ones with a full job console output.
Job after this set of PR: https://ci.ros2.org/job/ci_turtlebot-demo_linux/116
|
Awesome 👍 |
http://setuptools.readthedocs.io/en/latest/setuptools.html#setting-the-zip-safe-flag