Turn a module into a package locally

[Nathan_Boyer]

@nilshg

You do using Revise; using MyPkg, and then when you edit the code in MyPkg those changes automatically get reflected in your session.

Only if you dev the package into your current environment or are working in the package’s environment.

@lewis

Final questions:

• should I start the notebook (my experiment and testing playground) with Pkg.develop()?
• Will this actually pick up changes from the working set even without committing?
• Will this avoid making a copy of the package (as it would for a remote package repo) since I, in effect, already have made a copy of the package?

Final answers:

• I didn’t actually read about your notebook and testing playground, but I think Pkg.develop is what you want for live testing of your code.
• Yes.
• Pkg.develop loads the package files exactly where they sit on your file system. No copies are made (unlike with Pkg.add).

I had some of the same confusions. Maybe the answers on my post will help you:

Response to Pkg.jl and Julia Environments for Beginners by Jules

jkrumbiegel.com - Pkg.jl and Julia Environments for Beginners Thank you so much @jules for the great writeup. That clarified a lot for me. Consider adding this as a tutorial to the Pkg documentation. The existing documentation is pretty barebones and missing some crucial details e.g. I don’t think shared environments and the @ symbol are mentioned at all. I have a few follow up questions that I hope you don’t mind if I ask openly here. My main use case is developing an unregistered packaged t…