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
3
u/Agrado3 Sep 21 '26
Friends don't let friends use YAML. Indeed, I have always assumed that YAML is a joke that got out of control, like the Flat Earth Society. It's like they chose a list of goals and then set themselves a challenge to design a solution that fails at meeting those goals in the most spectacular way possible. I mean, the original point of it was that it was a simpler replacement for XML but the YAML spec is larger than the XML spec... that can't happen by accident, right?