# Hard to find bug in julia 1.0.0

**URL:** <https://discourse.julialang.org/t/hard-to-find-bug-in-julia-1-0-0/14404>\
**Category:** General Usage\
**Created:** [September 1, 2018, 1:24pm UTC](https://discourse.julialang.org/t/hard-to-find-bug-in-julia-1-0-0/14404 "2018-09-01T13:24:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [September 1, 2018, 2:16pm UTC](https://discourse.julialang.org/t/hard-to-find-bug-in-julia-1-0-0/14404/2 "2018-09-01T14:16:23Z")

</div>

Check for left over deprecations maybe? You really should be using 0.7 when upgrading code from 0.6.

> [@PSA: use Julia 0.7 if you are upgrading](https://discourse.julialang.org/t/psa-use-julia-0-7-if-you-are-upgrading/13321):
>
> A lot of people are posting issues where their old code doesn’t work anymore on 1.0 because some function has been renamed or removed. The 0.7 release exists exactly for this reason: your old code will work on 0.7 and give you a specific warning about how to fix your code. If you have any old code, you should use 0.7 to get these warnings before switching to 1.0; even if you just have work habits that may need changing, you should probably use 0.7 for a while. If someone posts an issue like thi…

---

_[View the full topic](https://discourse.julialang.org/t/hard-to-find-bug-in-julia-1-0-0/14404)._