20.3 Python Scope Decisions [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

===== 20.3 Python Scope Decisions =====

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:20-risks-and-open-decisions:start | Return to Risks and Open Decisions ]]

The team must decide the scope of Python in Phase 0. Python may support repository setup, prerequisite validation, type-generation orchestration, configuration checks, log inspection, test harnesses, documentation generation, and Evidence preparation.

Open Python decisions may include:

  - Role applicability for developers, testers, reviewers, CI runners, demonstration operators, and deployment environments.
  - Supported Python version range.
  - Dependency mechanism, such as requirements.txt, pyproject.toml, or another approved approach.
  - Scope of Python utilities as developer-support tools.
  - Use of Python in any runtime Node.
  - Use of Python scripts to generate support Artifacts, reports, checklist-derived automation, validation output, or Evidence packages.

The team should avoid allowing Python utilities to become hidden architecture. If a Python script encodes naming conventions, topic mappings, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] lists, configuration rules, or validation rules, the team should document those rules in the handbook, catalogues, or source definitions.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>