You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the package relies on Base.names to find out all the variables that are defined in the submodule containing the target of @frompackage.
This unfortunately does not expose the names of the variables that are imported in a module when simply using other packages.
See https://discourse.julialang.org/t/get-all-names-accessible-from-a-module/98492
This means that the behavior of @frompackage can not exactly mimic the chain of inclusions inside of the target Package source code.
It seems this also applies to names explicitly imported with the synthax using Package: name. Doing import Package: name does instead make the imported name visible also when calling using * in @fromparent
Right now the package relies on
Base.names
to find out all the variables that are defined in the submodule containing the target of@frompackage
.This unfortunately does not expose the names of the variables that are imported in a module when simply
using
other packages.See https://discourse.julialang.org/t/get-all-names-accessible-from-a-module/98492
This means that the behavior of @frompackage can not exactly mimic the chain of inclusions inside of the target Package source code.
Take as example the two notebooks inner_notebook1.jl and inner_notebook2.jl in the TestPackage
While inner_notebook2.jl should still se BenchmarkTools as it's imported within inner_notebook1.jl, this does not happen inside Pluto:
The current workaround is to also explicitly use the package also inside
inner_notebook2.jl
. So translate the macrocall frominto
The text was updated successfully, but these errors were encountered: