LabVIEW Python Node and externally installed Python interpreter bitness and version interoperability

Goal: Call Python functions from a Windows desktop LabVIEW VI using the Python Node with an externally installed interpreter.

LabVIEW does not include a Python interpreter, so the target Python installation must be selected and matched to the LabVIEW application instance. The documented constraint is that LabVIEW bitness must match the Python interpreter bitness; otherwise the Python DLL fails to load. NI also publishes a supported Python version range for each LabVIEW release, so a newer Python 3.x release may be unsupported by an older LabVIEW version even when bitness matches.

Uncertainty remains about which Python versions are supported by a specific LabVIEW release and whether installing Python after LabVIEW requires manual path configuration or repair of the Python Node integration.

Which Python versions does a specific LabVIEW release support through the Python Node? Which interpreter path does LabVIEW use when multiple Python installations exist? What behavior indicates a bitness mismatch between LabVIEW and Python?