JuliaPy / JuliaPy/PythonCall.jl
Lazy load CondaPkg (and Pkg), I think LazyModules for that, or better option?
- Langage dominant
- Julia
- Étoiles
- 1.1k
- Forks
- 86
- Merge moyen
- 1 j 22 h
- PR mergées (30 j)
- 3
Description
At least when I set:
ENV["JULIA_CONDAPKG_BACKEND"] = "Null"
I get: ERROR: InitError: CondaPkg is using the Null backend but Python is not installed
though, so not investigating further (I have Python installed).
With this one loads but not any faster (but should too):
```
ENV["JULIA_PYTHONCALL_EXE"] = "@PyCall" # optional
julia> ENV["JULIA_PYTHONCALL_EXE"] ="/usr/local/bin/python3";
julia> @time using PythonCall
┌ Warning: Python library "/usr/local/lib/python3.12/config-3.12-x86_64-linux-gnu/libpython3.12.a" could not be opened.
└ @ PythonCall.C ~/.julia/dev/PythonCall/src/C/context.jl:122
┌ Warning: Python library "/usr/local/lib/libpython3.12.a" could not be opened.
└ @ PythonCall.C ~/.julia/dev/PythonCall/src/C/context.jl:122
ERROR: InitError: Could not find Python library for Python executable "/usr/local/bin/python3".
If you know where the library is, set environment variable 'JULIA_PYTHONCALL_LIB' to its path.
```
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reproducing the CondaPkg Null-backend error and the PythonCall initialization failure described in the issue, then inspect how CondaPkg and Pkg are loaded. The referenced warning originates at ~/.julia/dev/PythonCall/src/C/context.jl:122; done should mean startup no longer eagerly loads these dependencies while the configured Python backends still initialize correctly.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- julia, python
- Domaine
- performance
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100