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
[WIP] import from asynchronous instead of async and fix python 3.7 compat issues #4679
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.
should be merged only after kombu 4.2 is released
should I address only import related issues in this pr? and other 3.7 related issues in another one? |
Please rename the PR and resolve all Python 3.7 related issues. |
I'm going to merge this anyway since we need this. I'm not sure why the build fails. |
…mpat issues (#4679) * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu in utils timer2 * update minimum kombu version
Latest Kombu renamed async to asynchronous celery/kombu#839 breaking Celery, which has a PR to fix this celery/celery#4679 but the changes haven't been released yet celery/celery#4387 so we use this in the interim.
…mpat issues (celery#4679) * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu in utils timer2 * update minimum kombu version
…mpat issues (celery#4679) * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu * imported from renamed asynchronous module of kombu in utils timer2 * update minimum kombu version
@auvipy Could we also apply this to celery 3.1.25? |
work to fix #4500