-
Notifications
You must be signed in to change notification settings - Fork 29
Open
Description
Say I have a module TopLevel that I want to @require a package (e.g., ProgressMeter)
module TopLevel
using Requires
__init__() = @require ProgressMeter="92933f4c-e287-5a05-a399-4b506db050ca" println("ProgressMeter loaded!")
using Main.SubModule # this uses ProgressMeter internally
endand I have a sub-module that itself uses ProgressMeter:
module SubModule
using ProgressMeter # used internal to "SubModule"
# ...
endThe TopLevel module will always think ProgressMeter is loaded because of a sub-module that uses it internally.
This means for the TopLevel package, I cannot @require any packages that are used by dependencies (some of which may be unknown to the developer of TopLevel, causing head-scratching behavior π)
Is there a way to ensure that the scope of the @required package is limited to modules "outside" the top-level module?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels