JuliaPy / JuliaPy/PythonCall.jl

Why must both PYTHON_JULIACALL_PROJECT and PYTHON_JULIACALL_EXE be set together?

Offen
#675 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Julia
Sterne
1.1k
Forks
86
Ø Merge
1 T. 22 Std.
Gemergte PRs (30 T.)
3

Beschreibung

I wanted to set my `PYTHON_JULIACALL_PROJECT` manually because i wanted to manage my julia dependencies manually, so i could use them both in julia (for testing) and via juliacall.
And because i didn't want them to be in my conda directory as that doesn't get version controlled and i wanted the manifest to get version controlled

But I didn't want to set my `PYTHON_JULIACALL_EXE` because I do not know where julia wil be installed on any of my collaborators machines and am happy to let them be worked out by juliapkg.

But i tried this and then got an error on `import juliacall`
```
Exception: Both PYTHON_JULIACALL_PROJECT and PYTHON_JULIACALL_EXE must be set together, not only one of them.
```

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start at the import juliacall entry point and trace how PYTHON_JULIACALL_PROJECT and PYTHON_JULIACALL_EXE are validated. Check how juliapkg resolves Julia when the executable variable is unset. Done means a manually managed project can be used without specifying the executable, while existing paired settings continue to work.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
julia, python
Bereich
tooling
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
38/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.