decorator-factory/typing-tips

collection of short articles about Python's gradual typing system

I'm a software engineer. Some of my interests include:

• Formal languages
• Functional programming
• Web development

Writing

• typing-tips, a collection of articles about Python's gradual typing system
• py-simpleparser — my hot take on parsing unstructured data

Linters

• flake8-useless-assert, a flake8 plugin to detect bad assert statements

• flake8-pep585, a flake8 plugin to find deprecated imports from typing (PEP 585)

• mypy-plugin-attempt — a demo plugin for mypy, a Python type checker

• pyright-playground (archived) lets you play with Pyright, a Python type checker, in your browser.

Experimental stuff and explorations

• lanim is a library for making animations in Python, built on functional programming principles
• elm-markup-language-demo — a Lisp-like markup language for writing articles (project for learning Elm)
• py-ast-rule-engine — search for patterns in Python code using a YAML specification
• ts-generic-rep — type-level lambdas, map, filter and reduce for TypeScript
• py-bot-command-parser — combinator parser for chat bot commands
• rs-interpreter-experiments — using different strategies to evaluate the same expression in Rust

Other platforms

• ⛳ Code Golf
• 🥞 Stack Overflow

Contact me

• Email: [email protected]
• Telegram: @decorator_factory
• Discord: decorator_factory

typing-tips's Issues

Organization of Typing Tips

Is your intention for this project to be a catalog of typing-tips or is there a specific order the articles should be read in?
If it's a catalog a good format is could be similar to java-design-patterns.

Feedback

This is really good! I read through it all and mostly have feedback around shiny new features you could be using, though obviously those depend on the Python version your audience is using.

• TypeVar: Does it make sense to focus on using bound= instead? I feel like bounded typevars are generally easier to understand than TypeVars with multiple constraints.
• Optional could also mention the | None syntax from 3.10, which is more explicit.
• Instead of NoReturn, 3.11 will probably allow Never instead.
• The TypedDict example could use typing_extensions.Required/NotRequired instead of the awkward MovieOptional base class.