BerriAI/litellm · error · ImportError

Could not create module spec for {local_file_path}

Error message

Could not create module spec for {local_file_path}

What it means

Import guard when loading a custom auth/plugin Python file: the file downloaded from S3/GCS exists but importlib.util.spec_from_file_location returned no module spec — the path is not a loadable .py module (wrong extension or unreadable file).

Source

Thrown at litellm/proxy/types_utils/utils.py:164

            from litellm.proxy.common_utils.load_config_utils import (
                download_python_file_from_s3,
            )

            success = download_python_file_from_s3(
                bucket_name=bucket_name,
                object_key=object_key,
                local_file_path=local_file_path,
            )
        else:  # gcs
            success = asyncio.run(_download_gcs_file_wrapper(bucket_name, object_key, local_file_path))

        if not success:
            raise ImportError(f"Failed to download {object_key} from {storage_type} bucket {bucket_name}")

        # Load the module from the downloaded file using the actual module name
        spec: Final = importlib.util.spec_from_file_location(module_path, local_file_path)
        if spec is None or spec.loader is None:
            raise ImportError(f"Could not create module spec for {local_file_path}")

        module: Final = importlib.util.module_from_spec(spec)
        spec.loader.exec_module(module)

        # Get the instance
        instance: Final = getattr(module, instance_name)

        # Clean up the temporary file
        try:
            os.remove(local_file_path)
        except Exception as cleanup_error:
            verbose_proxy_logger.warning("Could not clean up temporary file %s: %s", local_file_path, cleanup_error)

        verbose_proxy_logger.info("Successfully loaded custom logger from %s", remote_url)
        return instance

    except Exception as e:
        raise ImportError(f"Failed to load custom logger from {remote_url}: {e}") from e

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Verify the downloaded file exists at the local path and is a valid Python module.

When it happens

Trigger: Thrown at litellm/proxy/types_utils/utils.py:164 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18). Data as JSON: /api/errors/b7c3382cd7014592. Report an issue: GitHub.