-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Circular dependency with Accessors 0.1.40 and julia 1.10 #192
Comments
I can confirm this. It becomes much worse if you add additional packages, e.g.,
gives
|
The upcoming 1.10.8 might solve these warnings: JuliaLang/julia#52511 (comment) |
Ran into this today. Any best practice suggestions as a workaround (assuming it's an upstream bug)? Should julia 1.10 users just pin Accessors to 0.1.39? |
This is definitely an upstream Julia bug, but I somehow thought it's fixed already... Apparently, not. Earlier, we worked around this by reverting weakdeps making them regular deps. I guess that's what I can do soon (unless others get to it earlier). |
Given the warning
in the error message, the issue will likely introduce a lot of latency, won't it? |
I built the tip of the backports-release-1.10 branch (what's being prepared for 1.10.8) and still found circularity (but note the message is clearer now)
|
But... there's actually no cycle, if I'm not mistaken? So this means there are still unfixed bugs in the 1.10 branch? |
The issue is that Dates and LinearAlgebra are in the default julia sysimage, thus are always loaded, so their exts are always triggered, which creates the cycle. On 1.11 this is avoided and 1.12 extensions are triggered by importing packages, not just whether they're loaded. (IIUC, @topolarity) |
Is it possible to backport this fix to 1.10? |
Could anyone please confirm if #193 is the correct and complete solution? |
Ran a quick test in both 1.10 and 1.11: added and precompiled without issue. |
When installing the latest Accessors 0.1.40 on julia 1.10 I get a circular dependency warning
It gives no warning on julia 1.11 or installing Accessors 0.1.39 (whose project is a bit different but not substantially so from 0.1.40). Maybe it is an upstream bug in julia 1.10?
The text was updated successfully, but these errors were encountered: