# Revise error stack trace

**URL:** <https://discourse.julialang.org/t/revise-error-stack-trace/39557>\
**Category:** General Usage\
**Created:** [May 15, 2020, 9:26pm UTC](https://discourse.julialang.org/t/revise-error-stack-trace/39557 "2020-05-15T21:26:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ericphanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ericphanson/32/215186_2.png) [@ericphanson](https://discourse.julialang.org/u/ericphanson)\
**Post date:** [May 15, 2020, 10:33pm UTC](https://discourse.julialang.org/t/revise-error-stack-trace/39557/3 "2020-05-15T22:33:27Z")

</div>

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](https://discourse.julialang.org/t/revise-cannot-transform-my-dataset/39177/23)) 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.

---

_[View the full topic](https://discourse.julialang.org/t/revise-error-stack-trace/39557)._