refactor classes to use __init__

[chdsbd]

I believe we previously used new to support Pylance. Now Pylance doesn't support new so we need to use init.

Mypy works either way, but this allows us to get Pylance working properly with auto complete.

related: #136

[sbdchd]

oh pyright is angry in CI, maybe it needs an update?

[bschnurr]

I dont believe an annotation is needed for self. At least I never see it in typeshed repo

[chdsbd]

I think the annotation is required here to handle the Optional case. You can find examples of this in the typeshed repository too:

https://cs.github.com/python/typeshed/blob/d1375f600cc4a7e7d81dcd9229c6abb933efda2a/stdlib/array.pyi?q=__init__%28self%3A#L24-L28

[bschnurr]

any eta?

[chdsbd]

@bschnurr We can make this change, but it breaks foreign keys for Pylance. Mypy still works though: #136 (comment)

[bschnurr]

@chdsbd found an alternative fix..

just remove def __init__(self, *args: Any, **kwargs: Any) -> None: ... from class Field and keep all the __new__ func definitions

django-types/django-stubs/db/models/fields/__init__.pyi

Line 124 in 842bcd6

def __init__(self, *args: Any, **kwargs: Any) -> None: ...

then the previous __new__ function signatures will be picked up

__new__ and __init__ signatures aren't matching.

pyright does have a check for this. reportInconsistentConstructor

now i see a proper signature

[bschnurr]

this is a pylance bug. working on a fix