You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
closes#3886
**Context**
Prior to this change, the ui_mode parameter in several parts of the
PyFluent codebase had an incomplete or slightly misleading docstring.
Users could pass either members of the UIMode enum or specific string
literals (e.g. "no_gui", "hidden_gui", etc.), but that flexibility was
not well documented. This ambiguity could lead to confusion about which
string names are valid and how they map to enum values.
**Change Summary**
Updated the docstrings in launcher.py, slurm_launcher.py, and
session_utilities.py to better describe accepted ui_mode values (both
enum and string forms).
Clarified which string names correspond to which UIMode values (e.g.
"no_gui_or_graphics", "no_gui", "hidden_gui", "gui", etc.).
Removed or refined outdated or redundant lines in the existing doc
comments.
Ensured consistency across the codebase about how ui_mode is explained.
Marked the PR to skip tests, since only docstrings were changed.
**Rationale**
Better user experience / usability: Clear documentation helps users (and
maintainers) know exactly what ui_mode values are supported.
Reduce confusion / errors: Users may try unsupported strings or misuse
the enum; this aims to guide them.
Maintain consistency: Before, docstrings in different modules had slight
variations or omissions. This change harmonizes those descriptions.
Low risk: Since only documentation is modified (no logic changes), this
is a safe improvement.
**Impact**
Documentation / developer experience: Anyone reading or using code
involving ui_mode will get more precise information on acceptable
values.
Minimal to no runtime impact: Because no functional logic was changed,
existing behavior remains unchanged.
Future maintenance: When extending or deprecating a ui_mode, future
contributors can rely on the docstrings being consistent across modules.
Testing: No tests should break (and the PR is marked [skip tests]), but
doc validation tools (if present) may pick up formatting or lint
changes.
---------
Co-authored-by: pyansys-ci-bot <[email protected]>
0 commit comments