Replies: 2 comments 2 replies
-
|
I think it makes sense to install IJulia - a development environment - in the global environment, since a user probably wants to use it for development across projects, rather than making it a per-project dependency. And I think it's too early to teach the advanced complexities of the path (as an alternative solution). I mean, these are not dogma, you also want to be pragmatic. I personally consider jupyter pretty essential for my coding, so I'd love to use it across projects, which is easier to do with Julia than with R, for instance. The main purpose for global environment is for tools that help with development, like a package that helps with unit tests and what not. IDEs fall here too, why not? The trick is to minimize dependencies, not to avoid them 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for the suggestion! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, all.
While reading the Notebooks section I was struck by the phrase "install the IJulia.jl backend" as the Environments section recommends "to keep the default environment very light, containing only essential development tools". As it stands, someone reading the sections in order might install IJulia.jl in the default environment despite not considering Jupyter Notebooks an "essential development tool".
I wonder if it would it make sense to move the Environments section up to be after the REPL section?
Beta Was this translation helpful? Give feedback.
All reactions