summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorJade Lovelace <software@lfcode.ca>2025-07-09 22:28:50 -0700
committerJade Lovelace <software@lfcode.ca>2025-07-10 11:52:29 -0700
commita5fa5508dbb03966a1e74012c57d13b7f5539335 (patch)
tree196754aa139668443eba6278802e4b64428f23a7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent40de82b434526744da778ed53c742c1282d9e75e (diff)
doc: Add necessary details to understand dep propagation
This section has been the subject of too many jokes about nixpkgs and nix overall being incomprehensible among people I know. In lieu of adding to the fray I've had a go at correcting the reasons I couldn't read it myself. I don't actually think the math is a problem; it's actually probably the more understandable part of the section once you actually understand the definitions. The missing definitions and leaving the truth table as an exercise to the reader really was not working for me though. I've also added what each dependency group is actually *for*. This hopefully makes the section easier to understand how it applies in practice. I generated the initial version of the table before reformatting it and removing pointless rows with: ```python def mapOffset(h, t, i): return i + (h if i <= 0 else t - 1) for h0 in (-1, 0, 1): for t0 in (-1, 0, 1): if t0 < h0: continue heading = f'{h0:3} | {t0:3}' for i in (-1, 0, 1): if h0 + i not in (-1, 0, 1): mapped = 'x' else: mapped = mapOffset(h0, t0, i) heading += f' | {mapped:>2}' print(heading) ```
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions