# Best practice to set limits for Julia version

**URL:** <https://discourse.julialang.org/t/best-practice-to-set-limits-for-julia-version/103254>\
**Category:** General Usage\
**Tags:** question\
**Created:** [August 27, 2023, 10:56am UTC](https://discourse.julialang.org/t/best-practice-to-set-limits-for-julia-version/103254 "2023-08-27T10:56:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![GHTaarn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ghtaarn/32/216007_2.png) [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Post date:** [August 27, 2023, 5:21pm UTC](https://discourse.julialang.org/t/best-practice-to-set-limits-for-julia-version/103254/2 "2023-08-27T17:21:25Z")

</div>

I tested this in a similar situation yesterday and it had no effect

> [@Package compatibility constraints](https://discourse.julialang.org/t/package-compatibility-constraints/103217):
>
> I put the following line into a Project.toml for a package and am trying to figure out what consequences it has: [compat] julia = "1.0 - 1.7" When I try to add this package in another package from Julia 1.9.3 it is accepted without a warning and I can use it without warnings or incorrect behaviour. What consequences should I expect with compatibility specifications in a package?

---

_[View the full topic](https://discourse.julialang.org/t/best-practice-to-set-limits-for-julia-version/103254)._