Fix: Correct handling of import module as alias in LPython semantic analysis

[amritamishra01]

Summary

This PR fixes an issue where import statements with aliases (e.g., import numpy as np) would load the module correctly but fail to register the alias (np) in the current scope. As a result, subsequent code using the alias (like np.array()) would fail with NameError: 'np' is not defined.

This patch updates the semantic analysis phase to ensure import aliases are correctly created and installed into the symbol table as ExternalSymbols.

Technical Changes

• Modified visit_Import in src/lpython/semantics/python_ast_to_asr.cpp:
  • Refactored the logic to merge module name extraction and module loading into a single loop.
  • Previously, these were handled in separate loops, causing the alias information (x.m_names[i].m_asname) to be lost before the symbol registration step.
• Implemented Alias Registration:
  • Added logic to check for the presence of an alias.
  • If an alias exists, the compiler now creates an ASR::ExternalSymbol_t in the current scope.
  • This symbol maps the alias name (e.g., np) to the loaded module symbol (e.g., numpy), mirroring Python's behavior.

Verification

I verified the fix using the following reproduction script repro.py:

import numpy as np
print(np.array([1, 2, 3]))

Before Fix: Compiling failed with: semantic error: NameError: 'np' is not defined

After Fix: The compiler successfully resolves the alias. Running with --show-asr confirms the creation of the ExternalSymbol:
np:
        (ExternalSymbol
            2
            np
            1 numpy
            numpy
            []
            numpy
            Public
        )
Fixes #2814

[amritamishra01]

Subject: Clarifying the CI Failure

Hi @certik ,

I noticed the CI checks are failing on the macOS-latest build, but all other 17/18 test cases are passing. It looks like the failure might be related to the known default Mac environment issue rather than my changes.

Could you please confirm if this requires any action on my end? If not, I'm ready to address any other review feedback you might have.

Thanks!

[amritamishra01]

Update: Rebased on the latest main and all CI checks are now passing (18/18).

I have verified the fix locally and confirmed the tests pass on the CI. This is ready for final review!