Best Debug Workflow for Dr Watson

WillHWThompson
Fri, 07 Apr 2023 19:49:50 +0000
Performance

I am extremely frustrated by my current workflow. There has to be a better way and I wanted to ask for advice.

Here is how I have been working. I use Dr. Watson for all of my projects. I write all my store all my source code in the /src dir of the project and will test and implement new features/debug in a .jl file in the scripts directory.

I write code in a .jl file and run them one by one in the REPL which works well. The problem comes when I am trying to debug/modify code I have already written in an src file. In order to load the changes to a file I have to restart the REPL which means I have to reimport all my packages. This process can take upwards of 30 seconds every time I want to change anything.

I have tried using Infiltrator but It seems to work sporadically. It won’t always activate when it hits a @infiltrator macro and will close the REPL if an error is encountered.

What I really want is an equivalent of the Ipython autoreload.
There seem to be lots of options like AutoReload.jl but I can seem to get them to work.
I also tried to use Pluto as I read it automatically included changes but I could not get it to work with DrWatson.

It seems like this must be a very common problem. Is there an easy way around it?

8 posts - 4 participants