This commit is contained in:
2025-08-25 19:25:05 +01:00
committed by Expo on server
parent 200b946ece
commit 0ee267ac93

View File

@@ -118,7 +118,7 @@ converts to a more asynchronous architecture using python <a href="https://docs.
Many of the things it was intended to replace are still operating as a motley collection written by many different people in
several languages (but mostly perl and python; we won't talk about the person who likes to use OCamL).
<h3>Writing python</h3>
<h3 id=python>Writing python</h3>
<p>We aspire to a coding standard, and the <a href="https://github.com/google/styleguide/blob/gh-pages/pyguide.md">Google python coding standard</a> is a pretty good one. We don't use their TODO system though (para <a href="https://github.com/google/styleguide/blob/gh-pages/pyguide.md#312-todo-comments">3.12</a>) and the function (re)naming in troggle is still work in progress (para. 3.16.4).
<p>We don't have any type hints in troggle. It is not a big enough project to be worth it - probably.
@@ -127,6 +127,8 @@ several languages (but mostly perl and python; we won't talk about the person wh
<p>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.
<p>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: <a href="https://github.com/duarte-pompeu/greatpytools2025/blob/talk/article.md">greatpytools2025</a>.
<hr />
<h3><a id="arch">Archived updates</a></h3>
<p>Since 2008 we have been keeping detailed records of all data management system updates in the version control system.