Fun thing, today (1 hour ago) the 13:th may i was lookig for a typechecker with AI in what is popular right now because these things changes. I have been following pyrefly and ty before. Then i decided to go with pyrefly and added it. Noticed it was 1.0.0 which as odd because that is very special. How could i have missed that. Then I checked the blog and saw it was released yesterday. What a happy surprise to get a 1.0 as fresh delivery straight in to my project. Nice work!
I wish there was a config to error when a inferred type is either Any or Unknown so we can spot these locations. The report has it, but seeing it in the IDE would be great
I use django-types(1), which is far from perfect but does a good enough job for my usecases.
I think that Django's magic isn't statically typecheckable, so I tend to avoid those features altogether. If it's not possible, you can still provide a custom stubs for your needs, or provide a custom abstraction that wraps the not-typechecked parts, or accept that some parts of your codebase are less safe to modify than others. Nothing perfect, but it works.
Maintainer here: that's not the expected experience. If you're able to share details about the project & file an issue on our Github, we can try to reproduce it and figure out what's going on.
Fun thing, today (1 hour ago) the 13:th may i was lookig for a typechecker with AI in what is popular right now because these things changes. I have been following pyrefly and ty before. Then i decided to go with pyrefly and added it. Noticed it was 1.0.0 which as odd because that is very special. How could i have missed that. Then I checked the blog and saw it was released yesterday. What a happy surprise to get a 1.0 as fresh delivery straight in to my project. Nice work!
I wish there was a config to error when a inferred type is either Any or Unknown so we can spot these locations. The report has it, but seeing it in the IDE would be great
There's an `implicit-any` error code
Wish Django Stubs dont need a Mypy plugin https://github.com/typeddjango/django-stubs
I use django-types(1), which is far from perfect but does a good enough job for my usecases.
I think that Django's magic isn't statically typecheckable, so I tend to avoid those features altogether. If it's not possible, you can still provide a custom stubs for your needs, or provide a custom abstraction that wraps the not-typechecked parts, or accept that some parts of your codebase are less safe to modify than others. Nothing perfect, but it works.
(1) https://github.com/sbdchd/django-types
Funny what HN randomly misses sometimes -- this is huge news! Congrats to you and the team.
thanks! :-)
It’s a memory hog! The other day it was using 2.5GB of RAM.
Maintainer here: that's not the expected experience. If you're able to share details about the project & file an issue on our Github, we can try to reproduce it and figure out what's going on.