Skip to content

Discrepency in kernel/env behavior #68

Open
@mat-adamec

Description

@mat-adamec

In a regular Jupyter Notebook, users have the option to choose which environment they run their notebook in by changing the kernel:

kernels

In cmsaf-jh, it seems like the kernel is restricted to your current active conda environment. This is slightly confusing, because it doesn't tell you it's using your active conda env; it just keeps it labeled as the 'Python 3' kernel. For example, if we create an environment:

conda create --name envtest
conda activate envtest
pip install pyhf

Then the list of kernels still looks like this:

kernels2

But

import pyhf

now works, indicating we're in the envtest kernel (as pyhf is not installed by default, so it gives import error without envtest activated).

Metadata

Metadata

Assignees

Labels

condainvalidThis doesn't seem rightminorFor low-priority issues that don't impede usage

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions