Return to Answer

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The directory of the executable (the solution you have selected)
• The working directory
• The directories in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.

Note that the environment variables are copied from mother process to child process. If you start gVim from a custom explorer (e.g. Joplin) that has been started before your installation of Python it could be that the custom explorer is ignoring the new value of the path environment variable.

You have to close and relaunch Joplin to get it to import the environment variables correctly.

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The directory of the executable (the solution you have selected)
• The working directory
• The directories in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.

Remarks:

The environment variables are copied from the mother process to child processes. If you start gVim from a custom explorer (e.g. Joplin, TotalCommander, FreeCommander) that has been started before your installation of Python it could be that the custom explorer is ignoring the new value of the path environment variable.

To make sure gVim is aware of the new value of the path environment variable: restart the custom explorer (Joplin, TotalCommander, FreeCommander) and restart gVim.

You can verify that gVim is aware of the new value of the path environment variable by running the following Vim command:

:echo $path

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The directory of the executable (the solution you have selected)
• The working directory
• The directories in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The directory of the executable (the solution you have selected)
• The working directory
• The directories in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.

Note that the environment variables are copied from mother process to child process. If you start gVim from a custom explorer (e.g. Joplin) that has been started before your installation of Python it could be that the custom explorer is ignoring the new value of the path environment variable.

You have to close and relaunch Joplin to get it to import the environment variables correctly.

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The folder of the executable (the solution you have selected)
• The folder in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.

Vim needs to find the python310.dll. Like all executable it will search in a number of folders (the list and the order depends on the version of Windows).

But the list always includes:

• The directory of the executable (the solution you have selected)
• The working directory
• The directories in the path environment variable (what I would suggest)

I recommend that you add %LocalAppData%\Programs\Python\Python310 (i.e.: C:\Users\YourUserName\AppData\Local\Programs\Python\Python310) to your path environment variable.