# Loading from parent scope in package

**URL:** <https://discourse.julialang.org/t/loading-from-parent-scope-in-package/112434>\
**Category:** General Usage\
**Created:** [April 2, 2024, 6:01pm UTC](https://discourse.julialang.org/t/loading-from-parent-scope-in-package/112434 "2024-04-02T18:01:02Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [April 4, 2024, 11:07pm UTC](https://discourse.julialang.org/t/loading-from-parent-scope-in-package/112434/35 "2024-04-04T23:07:29Z")

</div>

Part of the original prompt was this would be a “pretty big library”, which is why we suggested the multiple package route.

> [@Code Organization](https://discourse.julialang.org/t/code-organization/112314):
>
> I’m having a really hard time finding a code structure that works for me. I’m building a pretty big library of interatomic potentials. I’ve broken the code up into several files: One for each of the following sets of tasks: Reading in crystal structure information and building associated datasets Processing calculation files and extracting information. Functions associated with Metropolis-Hastings algorithm and other machine learning stuff. A Lennard Jones library (I know, simplistic… for no…

I’m unclear if this project will be so that it requires a separate registry, but that is an option. One example for an academic group is @tim.holy 's lab’s registry:

> **[GitHub - HolyLab/HolyLabRegistry: Julia package registry for the Holy lab at...](https://github.com/HolyLab/HolyLabRegistry)**
>
> Julia package registry for the Holy lab at Washington University in St. Louis - HolyLab/HolyLabRegistry

---

_[View the full topic](https://discourse.julialang.org/t/loading-from-parent-scope-in-package/112434)._