Isolate meta-path importer installation
Open
Nobody has claimed this yet.
Needs Triage
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
In this Mercurial issue, I captured an issue where when setuptools invokes the Mercurial build script, that build script installs a meta-path importer. Setuptools sandboxing technique should additionally remove any meta-path importers installed as part of the build process.
Contributor guide
No contributing guide indexed for this repository
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 by reading setuptools' sandboxing implementation and Python's meta-path importer behavior, then use the linked Mercurial issue as the reproduction context. Done means the sandbox removes meta-path importers installed during a build without disturbing pre-existing importers, with regression coverage for that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100