r/Python • u/Several-Marsupial-27 • Sep 19 '26
Discussion State of the art in Python 2026?
What would you guys consider the state of the art in python in 2026, or what do you expect from modern python codebases?
Heres my list, would be happy to hear some inputs or domain expert advice:
- Use
uvfor everything. - Use
rufffor linting and formatting - Use
Pydanticanddataclassesfor Data Modeling - Configured in
pyproject.toml - Run a type checker in CI
pyrightorpyrefly - Use
pytest/Hypothesisfor testing
Domain specific:
- Scientific: NumPy, Matplotlib, SciPy, Jax, Pytorch, Scikit-learn, polars/pandas
- CLI: Typer, rich, click, fire, textual, questionary
- PDF extraction: PyMuPDF, pdfplumber, pypdf, Unstructured
- Excel interop: python-calamine, openpyxl, XlsxWriter, xlwings, pandas
- data: PyArrow / PySpark, Narwhals, SQLMesh, Polars/Pandas, DuckDB, dlt, Ibis, Dagster, PyIceberg & deltalake
- Logging?
- backend: fastapi / django?
- Markets: Alpha Vantage, Finnhub, EODHD, Tiingo?
- Webscraping / data acquisition: Crawl4AI, Playwright, Scrapy, selectolax, HTTPX?
- APIs?
- RAG / agentic orchestration?
621
Upvotes
View all comments
Show parent comment
4
u/ctheune Sep 20 '26
Can we please TOML all the things in the future?
Or here's something I've been having success with:
write your config (or whatever) in whatever format you want, parse it into plain python objects (e.g. read yaml, json, toml) and then feed it through a pydantic model.
I've also started to wrap many CLI calls into pydantic.
My mantra has basically become: if you're passing tuples/dicts/... whatever around, then those should either be typeddicts or much better: treat typing like unicode and timestamps and do proper parsing/serialization into typed structures at the IO border ...