Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Importing nested import paths #2062

Merged
merged 2 commits into from
Feb 21, 2025
Merged

Importing nested import paths #2062

merged 2 commits into from
Feb 21, 2025

Conversation

oxisto
Copy link
Member

@oxisto oxisto commented Feb 20, 2025

This is my attempt of interpreting the rules of python imports. I am not sure if this really reflects https://docs.python.org/3/reference/simple_stmts.html#the-import-statement but it reflects what happens when I execute CPython.

Fixes #2060

Copy link

codecov bot commented Feb 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.35%. Comparing base (dc61a28) to head (13c1fc4).
Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing lines Coverage Δ
...fer/aisec/cpg/frontends/python/StatementHandler.kt 86.66% <100.00%> (+0.19%) ⬆️

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@oxisto oxisto merged commit 1132231 into main Feb 21, 2025
4 checks passed
@oxisto oxisto deleted the fix-python-imports-again branch February 21, 2025 10:03
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Imports in python are not solved correctly
2 participants