3 ms·
Sadly I can not point you to a single piece of documentation that covers everything. That's definitely an area Julia can improve. Writing down the things "every
by oxinabox 7y ago
Sadly I can not point you to a single piece of documentation that covers everything. That's definitely an area Julia can improve.
Writing down the things "everyone" does, so newcomers don't have to learn them again.
The Pkg manual doesn't have a tutorial on standard practice.
But it's worth reading the compat section and making sure to always set your compats
https://julialang.github.io/Pkg.jl/v1/compatibility/ https://julialang.github.io/Pkg.jl/v1/compatibility/
And the section on creating one's own project. So as not to need to use the global environment.
And alternative to using `activate` after starting Julia (and my preferred way) is to start Julia with the `--project=.`
https://julialang.github.io/Pkg.jl/v1/environments/#Creating-your-own-projects-1 https://julialang.github.io/Pkg.jl/v1/environments/#Creating...
And can go further and create projects via PkgTemplates which is was "everyone" does.
Because a good project looks just like a package (one might as well consider them synonyms when looking for thus kind of advice)
https://github.com/invenia/PkgTemplates.jl/tree/v0.6.3 https://github.com/invenia/PkgTemplates.jl/tree/v0.6.3
- dnautics 7y agoIt's got anaconda-like project spaces? While I can see why they did that because it's what people are used to... That's a terrible, terrible choice (I joke there's a reason why docker got invented and it's that conda is awful). Why not just put deps in the project directory instead of in ./julia/..