Nimblesite / Nimblesite/Basilisk
[LSPUV-LOCK-IMPORT-MAPPING] site-packages top-level-module scan (mechanism 1) not implemented
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 54
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Spec: LSPUV-LOCK-IMPORT-MAPPING
Spec says:
Import names are mapped via three mechanisms; mechanism 1 scans the package's installed directory in site-packages for its real top-level module.
Code does:
Only mechanism 2 (a ~65-entry known table) and mechanism 3 (normalised fallback) exist. Packages whose top-level module is not in the table resolve to the wrong import name.
Location: crates/basilisk-uv/src/import_map.rs
Severity: critical · code logic does not match the spec.
Source: spec↔code conformance audit (PR #203). Full catalogue: docs/plans/SPEC-CONFORMANCE-AUDIT-PLAN.md → CONFAUDIT-CODE-BUG.
Fix per CLAUDE.md TDD bug process: add a failing test that encodes the spec requirement first, then fix the code — never weaken the test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with crates/basilisk-uv/src/import_map.rs and the LSPUV-LOCK-IMPORT-MAPPING section of the specification. Follow the TDD bug process in CLAUDE.md by adding a failing test for mechanism 1, then implement site-packages scanning so packages outside the known table resolve to their real top-level module; the test should pass without weakening it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100