search

alexmojaki / birdseye

Graphical Python debugger which lets you easily view the values of all evaluated expressions
https://birdseye.readthedocs.io
MIT License
1.65k stars 71 forks source link

No module named 'birdseye', windows 10, jupyter lab #72

Closed Dene33 closed 5 years ago

Dene33 commented 5 years ago

Trying to use birdseye with %load_ext birdseye in jupyter lab, win 10. Getting error ModuleNotFoundError: No module named 'birdseye' On another machine with win 7 - everything's perfectly fine.

Tried different approaches - with conda, virtualenv, different python versions, etc. No result.

alexmojaki commented 5 years ago

Does import birdseye work in the same notebook? What about outside a notebook?

Dene33 commented 5 years ago

Does import birdseye work in the same notebook? What about outside a notebook?

import birdseye doesn't work inside notebook. Everything's fine outside.

alexmojaki commented 5 years ago

This sounds like an issue with your notebook setup that probably has nothing to do with birdseye. birdseye is a pretty normal package as far as pip install goes.

Do any other pip-installed packages behave like this?

Does sys.version have the same value both inside and outside the notebook? How does sys.path compare? What if you set sys.path = <value outside notebook> inside the notebook?

Dene33 commented 5 years ago

This sounds like an issue with your notebook setup that probably has nothing to do with birdseye. birdseye is a pretty normal package as far as pip install goes.

Do any other pip-installed packages behave like this?

Does sys.version have the same value both inside and outside the notebook? How does sys.path compare? What if you set sys.path = <value outside notebook> inside the notebook?

I've looked into my sys.path and it seems that you're right. I have some mess there. Fixed it and now everything's fine.

It was a problem with jupyter kernel settings. Somehow the path to the kernel was wrong, pointing to kernel inside another virtual environment. Removing kernel with jupyter kernelspec remove kernel_name solved the problem. After removing it, Jupyter automaticaly created a new kernel pointing to the one inside curent virtual environment.