# Why some variables in a package are not properly included when calling that package

**URL:** <https://discourse.julialang.org/t/why-some-variables-in-a-package-are-not-properly-included-when-calling-that-package/116638>\
**Category:** General Usage\
**Tags:** question\
**Created:** [July 4, 2024, 10:03pm UTC](https://discourse.julialang.org/t/why-some-variables-in-a-package-are-not-properly-included-when-calling-that-package/116638 "2024-07-04T22:03:59Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![abulak](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abulak/32/28314_2.png) [@abulak](https://discourse.julialang.org/u/abulak)\
**Post date:** [July 5, 2024, 1:10pm UTC](https://discourse.julialang.org/t/why-some-variables-in-a-package-are-not-properly-included-when-calling-that-package/116638/12 "2024-07-05T13:10:44Z")

</div>

I’m the author of SymbolicWedderburn.jl 😉 and sorry for taking time of everybody here ;D, but the problem is very simple:

@Khashayar-Neshat You’re trying to run examples from master branch while using the released version of the package. This is bound to fail, given the number of changes in the current master.

[as I’ve already stated](https://discourse.julialang.org/t/symmetry-reduction-in-sumsofsquares/115727/15), I only haphazardly update `examples` folder while developing the next release.

If you can’t make them work, it’d be better to open an issue in the repository directly.

---

_[View the full topic](https://discourse.julialang.org/t/why-some-variables-in-a-package-are-not-properly-included-when-calling-that-package/116638)._