Skip to content

Using conda environment on remote #6

Description

@mick-d

First of all, great package, that's exactly what I was looking for. I still have an issue with using the remote conda environment: I am not sure the conda environment on the remote is used properly.

Ideally I would like to source it but the only option I found was to indicate the path of the remote conda environment python binary in kernel spec.

So when importing sys in the local notebook using the remote kernel, i get the correct environment python version (3.5):

sys.version
`3.5.1`

But clearly, the environment variables are not right (conda environment was clearly not sourced):

!python --version
Python 2.7.11

Is there a way to properly source the whole remote conda environment instead of just using its associated python binary?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions