# Problems with signature changes of imported local modules on include

**URL:** <https://discourse.julialang.org/t/problems-with-signature-changes-of-imported-local-modules-on-include/104842>\
**Category:** General Usage\
**Tags:** module\
**Created:** [October 11, 2023, 10:26am UTC](https://discourse.julialang.org/t/problems-with-signature-changes-of-imported-local-modules-on-include/104842 "2023-10-11T10:26:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Post date:** [October 14, 2023, 11:18am UTC](https://discourse.julialang.org/t/problems-with-signature-changes-of-imported-local-modules-on-include/104842/3 "2023-10-14T11:18:10Z")

</div>

It’s not clear to me what your actual complaint/question is, but one problem is clear: you `include` multiple copies of the same files (that happen to contain modules).

What you almost surely want to do instead, especially as a beginner, is to only use `include` at the top-most level.

Similar thread:

> [@Problem with referencing modules](https://discourse.julialang.org/t/problem-with-referencing-modules/100916/11):
>
> One issue that is apparent from the given warnings is that you have multiple conflicting copies of identical modules. You could probably fix this by adopting the practice of not includeing files from within your modules. If you’re deveping a package, then only use include in the top-level file/module. Keep in mind that include literally includes the contents of a file within another file. Try includeing each of your modules individually, from a fresh REPL session. EDIT: in case an example wo…

NB: corrected the category from “internals” to “general usage”.

---

_[View the full topic](https://discourse.julialang.org/t/problems-with-signature-changes-of-imported-local-modules-on-include/104842)._