When I’m not in a Project directory, I can make a file like so: # M1.jl module M1 export M1Type struct M1Type data::Real end end and then from that directory: push!(LOAD_PATH, pwd() and then using M1 and that all works just fine. But if I’m in a Project directory (I have a …

[image] tuckermcclure: Thanks for the quick reply! I’m unclear why that’s different when I’m in a Project directory than when I’m in a bare directory. It makes simple organizational tasks sort of strange, or I’m missing the right idiom for it perhaps. I think there are some things in the load…

dev path/to/M1? where M1 has a Project file itself. If M1 is not a package then do indeed use include.

Thanks for the quick reply! I’m unclear why that’s different when I’m in a Project directory than when I’m in a bare directory. It makes simple organizational tasks sort of strange, or I’m missing the right idiom for it perhaps. As I understand it, in a bare directory, this works fine: # M1.jl mod…

I think I follow you. I’m happy to leave the LOAD_PATH alone; I never actually liked that solution. You’re proposing to “upgrade” any local modules that need to be used in numerous places to full packages (with Project.toml files), and ]add them to the active project by their local paths. Alternate…

[image] tuckermcclure: You’re proposing to “upgrade” any local modules that need to be used in numerous places to full packages (with Project.toml files), and ]add them to the active project by their local paths. Yes, except probably use ]dev

dev the packages in the right order or possibly together. Or if you have more than a few local packages to juggle with, consider taking the next step and make your own registry with LocalRegistry . Alternatively, if they are of general interest, register them in the General registry.

As I understand it, in a bare directory, this works fine: # M1.jl module M1 export M1Type struct M1Type data::Real end end # M2.jl module M2 using M1 function f(x::M1Type) ... end end # At the REPL using M1 using M2 f(M1Type(1)) This code doesn’t seem to…

Hi @peterj , I think your first using M1 needs to be using ..M1 (from the parent module). Your second using M1 needs to be using .M1 (for a local module), and the same for M2. Also, note that M2 does not export f presently, so you’ll need to add that.

Thanks, I didn’t know about the .. thing I still get an error, actually the error I was trying to reproduce when I found this thread! # M1.jl module M1 export M1Type struct M1Type data::Real end end # M2.jl module M2 using ..M1 export f function f(x::M1Type) …

How to use local module within a Project directory?

New to Julia

tuckermcclure April 1, 2020, 7:04pm 8

Hi @kristoffer.carlsson, I know this is old, but as I’ve grown with this approach, there’s a new problem: "Unsatisfiable requirements" when local packages use local packages (fixed in v1.4)

Topic		Replies	Views
How to load a module from the current directory? New to Julia	5	14476	February 13, 2021
Magic incantations to make a local module work General Usage	10	822	April 11, 2020
How to 'using a_local_module' New to Julia	5	501	March 17, 2021
Modular local projects and `include(...)` New to Julia question , modules , code-organization	8	669	March 10, 2023
Julia cannot find the module file in the same directory of the main file General Usage question , package	3	1026	November 11, 2021

How to use local module within a Project directory?

Related topics