nixpkgs/pkgs/development/compilers/julia
Jim Garrison 1030f5772d julia: switch from python2 to python3
Julia does not actually require python2; it just requires any version of python
[that is equal to or greater than 2.7](https://github.com/JuliaLang/julia/blob/master/doc/src/devdocs/build/build.md#required-build-tools-and-external-libraries).

This changes the python dependency from python2 to python3.

I have verified that julia-1.0 builds with this change.  julia-1.5 is marked as broken
in nixpkgs, so I have not tested it (but I would be very surprised if this change
broke it further).

Motivated by #148779
2021-12-06 19:37:42 -05:00
..
patches julia_10-bin: deprecate 2021-12-02 01:18:07 +00:00
1.0.nix julia: switch from python2 to python3 2021-12-06 19:37:42 -05:00
1.5.nix julia: switch from python2 to python3 2021-12-06 19:37:42 -05:00
1.6-bin.nix julia_16-bin and julia_17-bin: punctuation fixes 2021-12-02 01:18:07 +00:00
1.7-bin.nix julia_16-bin and julia_17-bin: punctuation fixes 2021-12-02 01:18:07 +00:00
README.md

Julia

Julia, as a full-fledged programming language with an extensive standard library that covers numerical computing, can be somewhat challenging to package. This file aims to provide pointers which could not easily be included as comments in the expressions themselves.

For Nixpkgs, the manual is as always your primary reference, and for the Julia side of things you probably want to familiarise yourself with the README , build instructions, and release process. Remember that these can change between Julia releases, especially if the LTS and release branches have deviated greatly. A lot of the build process is underdocumented and thus there is no substitute for digging into the code that controls the build process. You are very likely to need to use the test suite to locate and address issues and in the end passing it, while only disabling a minimal set of broken or incompatible tests you think you have a good reason to disable, is your best bet at arriving at a solid derivation.