-
-
Notifications
You must be signed in to change notification settings - Fork 945
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
Plan to annotate - Kombu #1511
Comments
Hey @Kludex 👋, We also offer priority support for our sponsors. |
Related to celery#1511
Related to celery#1511
Related to celery#1511
Is there any priority? I can help with some of this tasks |
Not really. Go ahead. 🙏 |
just avoid duplicated work, so checking open or closed PR will help to avoid that |
Created a PR to no duplicate work |
I didn't forget about this. I'm struggling with time. JFYK. |
I was thinking of stubs instead of annotating the codes directly |
Why? |
Hi @auvipy, I wanted to continue working on type hints for Are you still open to have type hints directly in both projects? I can understand the drawbacks of having them in the source code (can block people contributing, extra CI checks, extra review for PRs adding typing), although there are benefits of having them builtin in the source code instead of stubs (never gets out of sync, readability for users of the library). If this is the case, I'd like to offer three things:
|
Fully Type Annotation - Kombu
Analogous to celery/celery#7394.
✅ (
:white_check_mark:
): Merged❌ (
:x:
): Need work💬 (
:speech_balloon:
): In reviewReport generated from
mypy kombu --txt-report .
(04/05/2022):The text was updated successfully, but these errors were encountered: