sesgoe

7 ms·

1. 1.▲
   by sesgoe 3y ago

   Please listen to this advice for anyone giving this a go after reading these comments. I was pretty green to the Python typing ecosystem when I started implementing it in our large pre-existing codebase, and I did not lean heavily enough on
2. 2.▲
   by sesgoe 3y ago

   > Rather than doing this, which does indeed seem like a headache, it may make more sense to skip import following at the very beginning until your core is typed so you can still enforce typing on the leaf nodes moving forward. Yea, this
3. 3.▲
   by sesgoe 3y ago

   There's a ton of motivation from a DX perspective -- Python type hinting's arguably least valuable feature is the autocompletion improvement that comes with it. It's nice to be able to hit `.` in your editor and have the opti
4. 4.▲
   by sesgoe 3y ago

   Yeah, this is something we tried! And yea, from an IDE perspective, it seems like maybe a sensible default would be to run `mypy ${CURRENT_FILE}` on save or something -- I've tried this manually myself, and it's decent , but it&#
5. 5.▲
   by sesgoe 3y ago

   From my experience working on an older Python codebase, this issue is definitely a headache. It's extremely difficult to gradually adopt typing in an older Python codebase with almost no typing information because the only real "e