Siblings of #4253: re-export forms the call resolver cannot follow

Open
#6,073 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Read the resolver work in PR #6071 and the related issue #4253 to understand the existing star re-export handling. This issue maps named JavaScript re-exports and Python from .x import * chains, but does not specify an implementation or tests. Done means the resolver can follow both forms; the issue names no test files.

Written by the indexing model from the issue text.

Description

core-engine enhancement priority: low scope:frontier

Class: re-export forms the resolver can follow. #4253 (PR #6071) covers export * from.

  • Named re-exports (export { x } from, export * as ns from): bind specific names, need a different mechanism
  • Python from .x import * chains: not star-tracked, still the 2-hop barrel expansion

No burned-estate program needs these. Mapped, not built. Siblings: #4253

Dominant language
Python
Stars
57
Forks
11
Avg merge
1h 35m
Merged PRs (30d)
975

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from squid-protocol/gitgalaxy

All issues in squid-protocol/gitgalaxy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.