I think I’ve seen stuff like that mostly when I have Revise acting on files with data, and then changing something causes it to rerun calculations / reparse data / etc. If that’s the case, I’d recommend the pattern discussed in a recent thread (Revise cannot transform my dataset - #23 by tim.holy) of separating “scripts” from package code, where the package code just has modules and functions but no data, and the scripts use the package code + data to do things. Then Revise just acts on the package code and updates functions as you want without issues from data and global state.
1 Like