Bump Julia to 1.5.3

[logankilpatrick]

Related to #89

[cbrewster]

Hey @logankilpatrick! Not sure if you've heard yet, but we are working on Nix support on Replit. Read more here: https://blog.replit.com/nix

This should make getting the latest version of Julia much, much easier. While, we are still developing our Nix support and there are some rough edges, it'd be great if you could give Nix + Julia a try. Please let me know if you run into any issues or if you have any feedback.

[logankilpatrick]

@cbrewster Awesome and exciting! Are there any specific steps I can do or the like to help out? Seems like folks in our community have been working on supporting Nix for some time: https://discourse.julialang.org/t/build-julia-on-nixos/35129/64

[573]

Should be sufficient:

# file replit.nix
{ pkgs }: {
    deps = [
        pkgs.julia_16-bin
    ];
}

.replit:

run = "julia -e 'println(\"Hello\");"

[cbrewster]

That looks like it should work, we do have a slightly old nixpkgs release so julia_16-bin may not be available yet. I will be updating that soon and we will have a regular, automatic nixpkgs update cadence (still in the works).

[IanButterworth]

Is there an eta on 1.6 to be provided? Or a way to trial it if there's a dev release?

[logankilpatrick]

Hey @cbrewster bumping this

[DilumAluthge]

It would be great to:

1. Get this PR merged.
2. Make another PR to upgrade to 1.6.2.

[DilumAluthge]

In particular, what I really want is for Julia 1.6.2 to come up by default when a user goes to https://replit.com/languages/julia, without any additional work or configuration needed on the user's part.

[lhchavez]

In particular, what I really want is for Julia 1.6.2 to come up by default when a user goes to https://replit.com/languages/julia, without any additional work or configuration needed on the user's part.

that's going to happen soon-ish! but that bright future is not going to involve polygott at all.

[DilumAluthge]

In particular, what I really want is for Julia 1.6.2 to come up by default when a user goes to https://replit.com/languages/julia, without any additional work or configuration needed on the user's part.

that's going to happen soon-ish! but that bright future is not going to involve polygott at all.

That's exciting!

Is there anything that we (Julia people) can do to help with the process? For example, is there a different repository to which we should make a pull request?

[lhchavez]

In particular, what I really want is for Julia 1.6.2 to come up by default when a user goes to https://replit.com/languages/julia, without any additional work or configuration needed on the user's part.

that's going to happen soon-ish! but that bright future is not going to involve polygott at all.

That's exciting!

Is there anything that we (Julia people) can do to help with the process? For example, is there a different repository to which we should make a pull request?

Thanks for the offer! :D Right now we don't have plans to have another open source repository for this (given our bad track record with this repository u__u), but the future we're building is going to give users a lot more power, and move all of the primitives needed to create your own shareable templates to repls so that we're no longer the bottleneck. This won't be limited to the nix packages that will be installed, but will also include choosing and configuring the interpreter, the LSP, and maybe even a debugger through the Debug Adapter Protocol. This means that in the near future we will be relying on the Julia community to maintain and own the Julia template(s)!

We're going to publish a blog post once all this is finalized and ready for public consumption. In the meantime, there are some questions that we'd like to get your opinion on to produce a second version of https://github.com/replit/prybar (the interpreter wrapper) that can be implemented completely within a repl (and significantly easier). Is this something we can reach out to the Julia community for opinions and/or help with? If so, what's the best forum to do so?

Once again, thanks :D and sorry for the delays here: we've learned from the polygott experiment and we're removing all the roadblocks in the future.

[DilumAluthge]

Is this something we can reach out to the Julia community for opinions and/or help with? If so, what's the best forum to do so?

Definitely! Probably the easiest approach would be to open an issue on the https://github.com/JuliaLang/www.julialang.org repository.

[rikhuijzer]

That looks like it should work, we do have a slightly old nixpkgs release so julia_16-bin may not be available yet.

Would it be possible for you to selectively set some packages to nixpkgs unstable by default? julia_16-bin is just a wrapper around the binary, so if unstable switches from, let's say, 1.6.2 to 1.6.3 and the tests pass, then it's quite save to move over.

With the stable release channel, it typically takes months before new releases are available.

[fingolfin]

Any news on this? By now Julia 1.6.3 is current (and in Nix) and 1.7 is coming soon.

BTW we noticed something weird: https://replit.com/languages/julia claims to offer Julia 1.3.1, but it really has 1.4.1 (can be tested by evaluating VERSION)

[IanButterworth]

I just tried and got julia 1.6.3, including the version hosted on the julia website https://julialang.org/learning/tryjulia/

That's great!

Worth noting though that 1.6.5 is the latest LTS, and 1.7.1 is the latest.

I assume there's been a move to a new system? How are updates handled now?