Since GeoDMS 20.23.1: the version labels of the interim builds name the release
The changes since 20.20.0 were labelled with the version of the build they first came in: 20.21.0,
20.22.0, 20.22.1 and, on one page, 20.23.0. None of those was published as a release that stayed;
20.23.1 is the first in all four flavours, so a reader on a released version could not tell from
the label whether their build has the change. Every "Since GeoDMS 20.21.0" and the like, also in
the forms "since 20.22.0", "*(since 20.21.0)*" and "_(20.22.0+)_", now says 20.23.1: 153 labels on
89 pages, replaced by one exact pattern and checked word by word in the diff, which holds only
version numbers.
By hand, where a version was named without "since": the order of the spatial index changed in
20.23.1 (Connect, Connect_neighbour, Deterministic-and-unspecified-results); Python-bindings says
"before 20.23.1" and "20.23.1 and later"; Arc-visualisation says the wide dashed pens were drawn
solid from 20.0.0 on and before 20.23.1; the "since version" of pareto_optimal and
pareto_optimal_eps is 20.23.1, and the epsilon of Impedance-options and impedance_matrix lost its
"relative since" that now named the same version twice. Left as they are: the two sentences on
what the interim builds 20.21.0 to 20.22.1 did with an epsilon, which is what someone who ran
those builds needs to know.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#1279 Listing the red items of a configuration from Python
Since GeoDMS 20.21.0 a script can ask an item for its meta info without calculating it, which
is what makes an item red in the GUI tree-view, and can read the fail reason of an item that
has not failed without the process dying.
Python-bindings.md gains a "Listing the red items of a configuration" section with the walker,
says why update_metainfo() and not update() (the latter reads the primary data of the item and
of all its suppliers, which for a raster attribute is a full calculation), and records what
changed about fail_reason(): before 20.21.0 calling it on a valid item took the whole Python
process down, so the only safe use was on an item already known to be bad. update_metainfo(),
in_template() and is_template() are added to the API reference, and GeoDMS-through-Python.md
points at them from its summary of the module.
Also corrected on the same page, unrelated to the above: the regular Windows setup stopped
carrying CPython 3.9 in 20.19.0 and now carries 3.12, 3.13 and 3.14; 3.9 is only in the GLOBIO
flavour. The page still named 3.9 among the four and asked release builders for PYTHON39_ROOT.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
updated doc wrt indirect expressions, https://github.com/ObjectVision/GeoDMS/issues/1142 and using pythion