From 0ee267ac93f040ec4e7f45db20f0f7645b1c08dd Mon Sep 17 00:00:00 2001 From: Philip Sargent Date: Mon, 25 Aug 2025 19:25:05 +0100 Subject: [PATCH] https://github.com/duarte-pompeu/greatpytools2025/blob/talk/article.md - online edit of handbook/troggle/trognotes.html --- handbook/troggle/trognotes.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/handbook/troggle/trognotes.html b/handbook/troggle/trognotes.html index bd3478e64..0bd3a04ed 100644 --- a/handbook/troggle/trognotes.html +++ b/handbook/troggle/trognotes.html @@ -118,7 +118,7 @@ converts to a more asynchronous architecture using python Google python coding standard is a pretty good one. We don't use their TODO system though (para 3.12) and the function (re)naming in troggle is still work in progress (para. 3.16.4).

We don't have any type hints in troggle. It is not a big enough project to be worth it - probably. @@ -126,6 +126,8 @@ several languages (but mostly perl and python; we won't talk about the person wh

We have run much of the code through black in 2022 so that is our default formatting standard.

We have also used ruff, isort and chill to trim and deduplicate the various pip installation packages and to fix the order of python packages in import statements. + +

Troggle was written when the python ecosystem was very immature. Today (2025) we can do a lot better. This suite of tools (uv and ruff configurations, mostly) is what we should be using on all troggle development machines: greatpytools2025.

Archived updates