psst VS pyre-check

On the other hand, this Rust-based one called Psst looks awesome and works: https://github.com/jpochyla/psst

Psst but currently very limited in features and have to build yourself.

psst, https://github.com/jpochyla/psst

I don't know how can I install this open source software from github.

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality).

You can also take a look at Psst. I use Symphonia for decoding and CPAL or CubeB for output. CubeB is a bit nicer.

There's also this project, written in Rust, which is a great GUI Spotify client https://github.com/jpochyla/psst

There‘s a Spotify client, psst, which has an Async widget (with a Promise state struct) that works very well for loading states etc. That project has a bunch of other tidbits and interesting patterns for Druid, I learned a ton from the code.

Did you come across pyre in your search? MIT license and pretty fast.

https://github.com/facebook/pyre-check

Pyre is a performant type-checker developed by Facebook. Pyre can analyse codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code.

Pyre from Meta, pyright from Microsoft and PyType from Google provide additional assistance. They can 'infer' types based on code flow and existing types within the code.

Have you seen Pyre[0]? Not Rust, OCaml, and pretty fast. Made by a team at Meta and open sourced on GitHub. If you use python-lsp, I wrote an extension[1] to enable integration (though I haven't tested it recently, been programming in rust; it is mostly a "for me" extension).

0: https://pyre-check.org/

1: https://github.com/cricalix/python-lsp-pyre

Internally we use Pyre for Python type checking: https://github.com/facebook/pyre-check

Before type hinting, work had intense rules and linters enforcing docstrings with types. Now, type hints and automatic pyre runs take care of all the heavy lifting.

Python now has an optional type system and if you add one of them such as mypy or pyre to your CI process and you can configure GitHub to refuse the pull request until types are added you can make it somewhat strongly typed.

If you have a preexisting codebase I believe the way you can convert it is to add the types that you know on commits and eventually you will have enough types that adding the missing ones should be easy. For the missing ones Any is a good choice.

https://pyre-check.org and https://github.com/python/mypy are popular.