# Module Not Reloading

**URL:** <https://discourse.julialang.org/t/module-not-reloading/5723>\
**Category:** General Usage\
**Tags:** module\
**Created:** [September 5, 2017, 9:30am UTC](https://discourse.julialang.org/t/module-not-reloading/5723 "2017-09-05T09:30:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![albi3ro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/albi3ro/32/1795_2.png) [@albi3ro](https://discourse.julialang.org/u/albi3ro)\
**Post date:** [September 5, 2017, 9:30am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/1 "2017-09-05T09:30:02Z")

</div>

I had a personal module that worked back in Julia 0.4.8 and I am in the process of updating it to Julia 0.6. I’ve updated all the syntax, but I have to change the name of the module from “Lattices” to “Lattices2” to get it to work.

Even though my “Lattices.jl” file has been updated to the new version, when I try `using Lattices`, I not only get errors about a package I don’t call anymore, but also none of my variables and functions get imported.

I’ve tried `reload("Lattices")`, but that does not help at all.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [September 5, 2017, 10:41am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/2 "2017-09-05T10:41:08Z")

</div>

Perhaps `Pkg.rm("Lattices") ` and then rename your `Lattices2`. Alt. remove it manually in `.julia/v0.6/`.

---

<div class="post-metadata">

**Author:** ![albi3ro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/albi3ro/32/1795_2.png) [@albi3ro](https://discourse.julialang.org/u/albi3ro)\
**Post date:** [September 6, 2017, 7:10am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/3 "2017-09-06T07:10:38Z")

</div>

`Pkg.rm("Lattices")` gives `INFO: Package Lattices is not installed`.

There is nothing to remove in ./julia/v0.6 either.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [September 6, 2017, 10:16am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/4 "2017-09-06T10:16:28Z")

</div>

Then it has to exist in a folder that is set in the `LOAD_PATH` variable.

---

<div class="post-metadata">

**Author:** ![albi3ro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/albi3ro/32/1795_2.png) [@albi3ro](https://discourse.julialang.org/u/albi3ro)\
**Post date:** [September 7, 2017, 3:26am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/5 "2017-09-07T03:26:59Z")

</div>

Does “.” count?

---

<div class="post-metadata">

**Author:** ![greg\_plowman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/greg_plowman/32/8100_2.png) [@greg\_plowman](https://discourse.julialang.org/u/greg_plowman)\
**Post date:** [September 7, 2017, 4:02am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/6 "2017-09-07T04:02:34Z")

</div>

Do you have a file/directory containing old `Lattices` module in your current directory?  
If so, then remove it.  
In any case, why do you want “`.`” in your LOAD\_PATH?

---

<div class="post-metadata">

**Author:** ![albi3ro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/albi3ro/32/1795_2.png) [@albi3ro](https://discourse.julialang.org/u/albi3ro)\
**Post date:** [September 7, 2017, 4:19am UTC](https://discourse.julialang.org/t/module-not-reloading/5723/7 "2017-09-07T04:19:44Z")

</div>

Found the problem. The same package existed elsewhere in on my computer. I thought I was loading the local one, but I was loading one at a different location.

Thanks for your time, and sorry it ended up being so silly. But I guess the problem is usually silly.