Maya Module Path: Deterministic Loading of Duplicate Module Names

Module Loading Precedence

Maya utilizes MAYA_MODULE_PATH to resolve dependencies, following a documented precedence order: user preferences, project settings, installation paths, and environment variables. However, when multiple .mod files with the same module name exist at the same precedence level, the internal loader must resolve which version to initialize.

Environment Isolation Constraints

For repeatable development environments across Maya 2022–2025, deterministic loading is critical. Because the embedded Python interpreter seeds sys.path from these module paths, any ambiguity in tie-breaking rules for identical module names can lead to inconsistent package versions across different operating systems or Maya patch releases.

While the Module Manager in Maya 2024 provides a UI for enabling and disabling modules, it manages state via user preferences rather than a project-level lockfile or strict versioning system.

• What is the specific tie-breaking mechanism used by Maya when two modules of the same name are found at the same precedence level?
• Is this resolution order guaranteed to be stable across different OS platforms (Windows vs. Linux) for a given Maya version?