-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
cannot build IJulia without disabling Julia's startup.jl #1097
Comments
Do any other packages work? |
Building BenchmarkTools, OffsetArrays, MacroTools and BangBang works, but it seems to me that building them is a no-op. Can you suggest a package to try? |
PyCall, MathJaxRenderer, Gurobi, and WinRPM are examples of other packages that have build scripts. (Note that the error here is from building Conda, not IJulia, by the way.) |
I've tried PyCall and Gurobi (both on a different machine, but again with InteractiveUtils in startup.jl). The result is the same. For PyCall the error is again triggered by Conda, and in the other case it is Gurobi itself:
Building IJulia and Gurobi with Julia 1.9.3 work fine. EDIT: Adding and building MathJaxRenderer works with Julia 1.10.0-rc1. However, |
In this case, the problem is not specific to any of these packages, but is something else, maybe something weird in your package environment. Since it's a general Julia question (not package-specific), I would start by asking on https://discourse.julialang.org/ |
I've just replaced Julia 1.10.0-beta3 with 1.10.0-rc1. Afterwards I wanted to build IJulia again. However, I always got the error message
Line 3 of my startup.jl is
using InteractiveUtils
. Sayingadd InteractiveUtils
at the Pkg prompt doesn't change anything. However, if I start Julia with--startup-file=no
, then it works without problems. I don't know if this is an issue with Julia, IJulia or Conda, or maybe none at all. If this is how it's supposed be, then maybe one could mention the necessary--startup-file=no
option in the documentation.The text was updated successfully, but these errors were encountered: