Support other package managers besides pip/conda

I’m using PEP582 featured Python package manager (e.g. PyFlow or PDM) which installs local packages in {project_path}/__pypackages__ folder.

The problem is that I did not find a way to set Jupyter Server to find ipykernel in {project_path}/__pypackages__. VSCode asks me to install ipykernel by pip, but I’ve already install it locally in {project_path}/__pypackages__.

I need a way to run a Jupyter Cell (ctrl + enter) in my python code with #%% which would find the ipykernel in {project_path}/__pypackages__.

1. How do I config Jupyter Server properly to find ipykernel in {project_path}/__pypackages__?
2. How do I config {project_path}/__pypackages__ for Python package search paths?

[xareelee]

The problem you’re having is specific to using a different package manager. So the request would be more like support other package managers besides pip and conda.

Yes, If only trying to solve my specific problem.

For abstract thinking in problem solving, I think the problem is: how to eliminate different behavior when launching a VSCode workspace with different ways (make it consistent).

I think there are many ways to solve this abstract question:

• specify additional module search paths for loading ipykernel in settings.json. (which currently is not available in general settings)
• make PYTHONPATH support finding ipykernel before launching. (which currently is not working in settings.json)
• give a way to setup environment for VSCode regardless how to launch it. (which currently is not working in .env)

That sys.path should be different if you run the same code from the gui launched VS code.

I found that setting $PYTHONPATH in VSCode doesn’t help launch python code by Command Palettes:

• Run code
• Python: Run Python File in Terminal
• Jupyter: Run Current Cell

the sys.path will not contain my local packages (__pypackages__/3.7/lib).

I have no idea that is a bug or not. I need a way to load my local modules in Jupyter, including finding local ipykernel when launching.

The reason it works when you run from the command line is the environment is setup correctly to find the packages you installed with the other package manager. VS code will inherit the environment from the command line shell. In fact this is the recommended way to get VS code to find packages when using conda too.

Thanks for your info, I finally know what is going on here.

[DonJayamanne]

Unfortunately there haven’t been enough upvotes on this feature request, hence closing this issue