ngam

@h-vetinari I have a question (I tried building torchtext and torchaudio, and failed; that's why I've been keeping an eye on your progress): Can we perhaps have a clearer strategy...

> Long story short: I think we don't need a big change in strategy, but more resources would help a lot, and especially a more aligned upstream maintainership. Fully agree...

Oh my days. Never heard of this one before 😅 @thewchan, what's the specific need here? What do you envision? We are trying to come up with a comprehensive policy...

We may need to investigate setting the right flags/env vars here https://github.com/cjdoris/pyjuliapkg#which-julia-gets-used and here https://github.com/cjdoris/pyjuliapkg#where-are-julia-packages-installed

No no, that's not the point. Please keep it open. We simply want to make sure we are supporting this in the best way possible, that's all. Let's try to...

@mkitti pls see this and #20379

I made the comment about pythoncall based on these files https://github.com/cjdoris/PythonCall.jl/tree/main/src So, is the python component alone enough? Why don't we package it like it is done upstream, with the...

I guess my confusion was from housing two distinct (presumably independent) packaged under one repo named as if it were a julia package... anyway, my personal vote would be to...

> Though note that if JuliaUp is also installed, JuliaPkg will use that instead of whatever is in the PATH - perhaps JuliaPkg could change its preference order in this...

Sorry re the lack of clarity. This answers my question. > * JuliaCall is a Python library for calling Julia functions from Python. It depends on JuliaPkg to install Julia...