Can't install Polars and DuckDB on windows 11

[eldee]

Glad I could help.

@pk1

First question is, how were you able to find this answer? In other words, what should I have done to find the solution myself.

Well, Google (or your favourite seach engine) and the Julia Discourse are your friends . When I got the error message that Polars could not be found (in the registry), I just googled to get to the github page. Most of the time you would find installation instructions, especially if it’s not just add <package>. In the absence of this I checked the Issues, where there indeed was one about registration. Now, I remembered that you could directly install packages from github, but if you wouldn’t, the first Google result for “Julia install package from github” is

Julia adding package from github

which is helpful.

For DuckDB I just searched for something along the lines of “precompile DuckDB” on the Julia Discourse, resulting in the topic I linked to. Again, I was already aware of the Pkg syntax to install a specific version, but that’s a quick Google search away. If I remember correctly

(@v1.11) pkg> add DuckDB@1.0

didn’t work, as it would still install a newer version of the _jll file, as evidenced by the output in the REPL, so I also forced the version here.

@pk1

The second question is, can you recommend any book(s), youtube video(s), or sites that offer good introductions to julia targeting already experienced developers (python, Rust, R)? There are a couple of good videos on youtube, but from simple data scientists that are not so good for my case.

I think it would be best to create a new topic. Well, first look around a bit on the Discourse to see if no similar question has been asked in the past. If not, I think posting under New to Julia is fine.

@pk1

The error on windows is:

I’m haven’t encountered this error before, but you could try the solution proposed here:

How to fix SSL cert issues in Pkg

I struggled with this for a while, and found that removing environment variables: SSL_CERT_FILE JULIA_SSL_CA_ROOTS_PATH made things work. At the windows powershell prompt, these can be removed manually (and temporarily, for testing) with: Remove-Item Env:SSL_CERT_FILE Remove-Item Env:JULIA_SSL_CA_ROOTS_PATH If you find this works, you can then remove them from your personal environment variables.