Skip to content

Bug introduced by JuliaCall 0.9.35 - mistakenly uses JULIA_PYTHONCALL_EXECUTABLE not JULIA_PYTHONCALL_EXE #813

Closed
#814
Closed
Bug introduced by JuliaCall 0.9.35 - mistakenly uses JULIA_PYTHONCALL_EXECUTABLE not JULIA_PYTHONCALL_EXE#813
#814
Labels
bugSomething isn't working

Description

@MilesCranmer
MilesCranmer
opened on Sep 9, 2026

Introduced by #781, it seems the wrong env var was set:

PythonCall.jl/pysrc/juliacall/__init__.py

Line 259 in 2cd566a

os.environ['JULIA_PYTHONCALL_EXECUTABLE'] = sys.executable or ''

This results in child threads requesting a new CondaPkg environment.

@cjdoris FYI

Activity

  1. MilesCranmer
    added
    bugSomething isn't working
    on Sep 9, 2026

  2. MilesCranmer commented on Sep 9, 2026

    @MilesCranmer
    MilesCranmer
    on Sep 9, 2026
    ContributorAuthor

    @MilesCranmerBot can you please make a PR fixing this?

  3. MilesCranmer commented on Sep 9, 2026

    @MilesCranmer
    MilesCranmer
    on Sep 9, 2026
    ContributorAuthor

    (I think this is why I am getting some conda-forge errors such as https://github.com/conda-forge/pysr-feedstock/actions/runs/34309470549/job/102332935050?pr=162)

  4. cjdoris
    closed this as completedin #814on Sep 9, 2026
  5. JamesWrigley
    added a commit that references this issue on Sep 9, 2026

    set JULIA_PYTHONCALL_EXE instead of JULIA_PYTHONCALL_EXECUTABLE in ju…

    80d2988
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions