Ta-da! You are running an app with its dependencies installed in an isolated place, while no virtualenv is involved.
For Windows users, please refer to [the doc](https://pdm.fming.dev/#enable-pep-582-globally) about how to make it work.
For Windows users, please refer to [the doc](https://pdm.fming.dev/latest/#enable-pep-582-globally) about how to make it work.
If you are curious about how this works, check [this doc section](https://pdm.fming.dev/usage/project/#how-we-make-pep-582-packages-available-to-the-python-interpreter) for some explanation.
If you are curious about how this works, check [this doc section](https://pdm.fming.dev/latest/usage/project/#how-we-make-pep-582-packages-available-to-the-python-interpreter) for some explanation.
and make sure VSCode runs using the same user and shell you enabled PEP582 for.
??? note "Cannot enable PEP582 globally?"
...
...
@@ -294,7 +294,7 @@ and make sure VSCode runs using the same user and shell you enabled PEP582 for.
```
If the above still doesn't work, it's most likely because the environment variable is not properly loaded when the Notebook starts. There are two workarounds.
1. Run `code .` in Terminal. It will open a new VSCode window in the current directory with the path set correctly. Use the Jupyter Notebook in the new window
2. If you prefer not to open a new window, run the following at the beginning of your Jupyter Notebook to explicitly set the path:
...
...
@@ -314,7 +314,7 @@ can be run natively as [VSCode Tasks][vscode tasks].