No module named hydra: check hydra-core, then the configuration search path
Hydra's common distribution name differs from its import name. A missing module and a missing configuration require separate repairs.
Scope and symptoms
Hydra's common distribution name differs from its import name. A missing module and a missing configuration require separate repairs.
Search fragments; wording and context vary:
No module named 'hydra'
MissingConfigException
Source-supported context
The Hydra introduction installs the hydra-core distribution and imports hydra. Its configuration system has application-specific entry points and search paths that are not validated merely by installing the package. V04-HYDRA
Distinguish these cases
1. An unrelated same-name distribution was installed, or hydra-core is absent from the intended interpreter.
2. Import works, but the configured search path points elsewhere. @hydra.main(config_path=...) is relative to the defining script; a relative file:// search-path entry is relative to the process working directory.
3. Configuration is present but references missing groups, overrides or a different application revision.
Suggested diagnostic sequence
This sequence is editorial guidance, not a diagnosis of your machine.
1. Check the node's declared dependency and hydra-core metadata in the actual environment. Distinguish ModuleNotFoundError from configuration exceptions.
2. Install the supported distribution for a genuine missing import. Record the environment before removing anything and establish any same-name collision rather than assuming one.
3. For configuration failures, preserve the searched paths and missing name. Check repository completeness and matching revisions; resolve each path according to its actual Hydra entry point before changing the startup directory.
4. Use the node author's supported configuration entry point for a minimal test, then restore overrides one by one. A YAML file from a different project is not a compatible replacement.
Completion checks
The intended configuration and required groups resolve and the minimal operation completes. Importing hydra alone does not validate the configuration chain.
Limits and cautions
Avoid arbitrary global PYTHONPATH or working-directory changes that hide a deployment problem. Redact secrets from configuration logs before sharing them.
Source review: 2026-09-27. No installation, GPU inference or user-environment repair was executed.
Original sources
- Hydra introduction · 2026-09-27
- Hydra config search path · 2026-09-27
Related guides
Was this page helpful?
Anonymous. Only a yes/no counter is stored; no account, IP address or device details.
Sources & references
Source-based editorial draft; no runtime verification. Version observations are scoped, and unknown wrapper identity is explicit.
01Hydra introductionSource checked: 2026-09-2702Hydra config search pathSource checked: 2026-09-27