Which type-checker are you using?
Which type-checker are you using?
@europython I went through 3/4th of the proposals so far. There are *too many* interesting proposals, even more so than previous years I find. What a nice predicament to experience!
Especially excited to see (relatively) many people wanting to share their stories and retrospectives (which has been historically lacking from soloists & small teams), #eventsourcing for all knowledge levels, and more nuances on #pythontyping (it's not a yes/no story for #python ).
Bumped to typing.cast() function, which has been there since Python 3.5. This blog post explained well what it does and when you might need it:
https://adamj.eu/tech/2021/07/06/python-type-hints-how-to-use-typing-cast/
Sometimes I contribute types to opensource projects, and while some projects are welcoming type contributions, others either not consider it a priority or even oppose including types.
For me typing greatly improves development process. How about you?
Are you using types in your projects?
@ambv so, what do you think about this problem?
It also behaves the same way in mypy. But here bug is not closed, and i'm hoping it can be fixed.
Turns out using `func(kwargs)`becomes very inconvinient, when you're using type-checking.
Pyright 1.1.312 landed a change:
> ... The new behavior matches that of mypy and assumes that the unpacked dict may supply arguments for all otherwise-unmatched keyword parameters even if they have default argument values.
https://github.com/microsoft/pyright/issues/5545
And now i need `# type: ignore` for each `kwargs`.
@hynek any ideas how to approach this?
Or maybe someone on #EuroPython ?