# Including multi-threading functionality in a package

**URL:** <https://discourse.julialang.org/t/including-multi-threading-functionality-in-a-package/35698>\
**Category:** New to Julia\
**Tags:** package, multithreading\
**Created:** [March 7, 2020, 9:00pm UTC](https://discourse.julialang.org/t/including-multi-threading-functionality-in-a-package/35698 "2020-03-07T21:00:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [March 8, 2020, 8:09am UTC](https://discourse.julialang.org/t/including-multi-threading-functionality-in-a-package/35698/3 "2020-03-08T08:09:34Z")

</div>

> [@joshuanunn](#):
>
> enforce it (but presumably limit users to Julia \>= 1.3)

IMO this is the only viable option for most open source projects with limited resources. Your users just have to switch to 1.3, which is the reasonable thing to do anyway (and soon, 1.4).

Generally, unless a package has users with [very low risk tolerance](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623), its maintainers should never hesitate requiring a released version. And conversely, users who claim they have very low risk tolerance and want to use your package on earlier versions should be ready to back this up with contributions in the form for PRs or money.

---

_[View the full topic](https://discourse.julialang.org/t/including-multi-threading-functionality-in-a-package/35698)._