Issue with typing in v0.12.0 about aiocache HOT 6 CLOSED

I've removed the py.typed file for the next 0.x release, so it go back to being untyped.
We'll focus on getting the type annotations working for the 1.0 release.

from aiocache.

Pretty sure 0.11 has no typing, so it's not a regression.

That class does some weirdness with __new__(), maybe adding annotations to that method will get mypy to figure it out. Otherwise, I think that's due for a refactor to make the implementation a bit simpler. There are already some tasks open to refactor parts for the 1.0 release, if you've got any time to help out and look at some of those, that'd help get us there quicker.

from aiocache.

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

from aiocache.

I just had a quick check, if I try to annotate __new__() I get more errors (e.g. that it must return a subclass of Cache, but it's actually returning a subclass of BaseCache).

I think refactoring this for 1.0 is going to be the best option. Maybe we should just remove the Cache class completely and get users to import the actual cache implementation they want to use? Would likely make things a lot simpler.

from aiocache.

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]

from aiocache.

See the comments above. I've disabled typing support until v1.

from aiocache.