Custom importer for use in Exocet modules
Registered by
Laurens Van Houtven
Inside Exocet modules, the import statement gets a new meaning. Stuff is injected by getting it from a context. That is the job of the custom importer. The custom importer also needs to temporarily disable the default importer mechanism.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)