-
Notifications
You must be signed in to change notification settings - Fork 154
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
Issue with typing in v0.12.0 #667
Comments
Pretty sure 0.11 has no typing, so it's not a regression. That class does some weirdness with |
Yes, I was not correct in my takes. 0.11 has no typing, but mypy returned issues about that Cache instance doesn't have some attributes. I will try chech it if I have a free time. Thanks |
I just had a quick check, if I try to annotate I think refactoring this for 1.0 is going to be the best option. Maybe we should just remove the |
I've removed the py.typed file for the next 0.x release, so it go back to being untyped. |
Hi, after upgrade from 0.12.0 to 0.12.1, I have this mypy error Skipping analyzing "aiocache": module is installed, but missing library stubs or py.typed marker [import] |
See the comments above. I've disabled typing support until v1. |
I have recently upgraded aiocache from 0.11 to 0.12 and after that mypy(v1.0) raised these errors below:
You can see in code below some usage of aiocache inside my service method:
Aslo when I downgrade aiocache from 0.12 to 0.11, It will work without any errors. So, I think the new version of aiocache has some issues with typing.
This is not critical issue, but I expect that someone can resolve it
The text was updated successfully, but these errors were encountered: