-
Notifications
You must be signed in to change notification settings - Fork 147
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
Replace trollius by asyncio #574
Replace trollius by asyncio #574
Conversation
CI failed as your patch is of course not python2 compatible. |
A version-agnostic implementation unfortunately does not seem to be possible because the new |
@mikepurvis How do you want to handle this version-incompatibility here then? |
Thanks for doing this work! Looks like the changes are pretty straight forward. Per @wjwwood's comment on #558 (comment), I'd be fine to just merge this and release it as 0.5.0, supporting Python 3.5+ and Ubuntu 16.04+ only. Trusty is five years old at this point, and ROS Indigo was EOL in April 2019. At the end of the day, |
@mikepurvis Sounds wonderful! Could you patch CI to remove the python2.7 checks then so CI succeeds here and this gets merged? |
You should be able to make the CI updates part of this change! Just update the travis config here: https://github.com/catkin/catkin_tools/blob/master/.travis.yml And |
This would be great, as this would make catkin_tools work with newer Python releases in the |
I wonder if you could use |
Given that the target OS will be 16.04+, it probably makes sense to have it testing against Python 3.5, but either way this is fine for now. Thanks for the contribution! Going to merge and then myself and others can use it from source for a bit before recommending a new release. |
Since trollius is a python2 package that is not necessary for python3 because the functionality has been replaced by the python
asyncio
module, this pull request replaces trollius by asyncio. It closes #520 and would close #558 because the dependency to trollius could be dropped.To be python3 compatible, #565 should also be merged.
Obviously, this pull request would drop python2 support, which is currently probably not realistic. Would it be possible to merge this to a separate branch to release a different version for python3?