Skip to content

use_condaenv() doesn't activate the specified conda env #1837

@ataeub

Description

@ataeub

When using use_condaenv() and then py_run_file() I expected use_condaenv() to activate the specified conda environment and run the python file within it. However it didn't do that. I found out, because in my conda env I have a custom activate script that adds some pythonpath variables. This worked when running the file via conda_run2() but not with use_condaenv() and py_run_file().

I don't know whether this is expected behaviour that's why I didn't post this as an issue, but it seems kind of counterintuitive to have a separate use_condaenv() function in addition to the use_python() function when the former doesn't activate the environment. Or am I missing another purpose of this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions