How to re-register .py file extension to new moved Python dir (on Windows)?

[pstein]

Assume I installed Python v3.1.3 in the default installation directory

C:\Program Files\Python\

Now I decide to move this installation directory (without re-installlation) e.g. to

D:\devtools\Python\

Unfortunately simply moving the installation directory breaks the file associations.
The same applies when I want to use Pything from flash drive.

*.py file association still points to the old directory.
and Environment variable PATH still contains the old Python location too.

So how can I tell Python to re-register itself (for file associations and PATH) by using its current new directory?

Any solution for that?

[popejose]

Find any .py file in explorer and right-click it. Choose "open with" and browse to your new python executable. Make sure to check the "always" box.

/regards

[snippsat]

Here how to change Environment Variables Path, remember to also add path to Scripts folder as image here.

Can use FileTypesMan for file associations.

[pstein]

Ok, thank you.

Thats means I have manually to fiddle around with system settings and context menüs.

There is no simple

python.exe -register

commandline command which does the job for me?

[snippsat]

Thats means I have manually to fiddle around with system settings and context menüs.

Is common to to fix add stuff to Environment Variables Path,
when programming this is very low requirement to understand and make changes to.

Can also just use py,it bypass Environment Variables(py.exe get install to windows folder) and have been in Python 3 for long time

G:\div_code
λ py --version
Python 3.13.0

G:\div_code
λ py --help
Python Launcher for Windows Version 3.13.0

usage:
py [launcher-args] [python-args] [script [script-args]]
.....

---

uv is the new Python package and project manager for Python.
Can start with no Python install on OS,uv will download and install.

G:\div_code\py_313
λ uv venv --python 3.13.0 # Will get Python 3.13 and install
Using CPython 3.13.0
Creating virtual environment at: .venv
Activate with: .venv\Scripts\activate
 
G:\div_code\py_313
λ .venv\Scripts\activate
 
G:\div_code\py_313
(py_313) λ python --version
Python 3.13.0

[DeaD_EyE]

Unfortunately simply moving the installation directory breaks the file associations.
The same applies when I want to use Pything from flash drive.

Same happens, if you move on Linux /usr/bin/python to another place, which is not in Path and then trying to run a Python program. The shell won't find the interpreter, because it's not in the PATH variable. On Windows, you have File Associations. You can see them in your Registry under the KEY: HKEY_CLASSES_ROOT\Python.CompiledFile\shell\open\command

Generally it's in the most cases not possible to move an installed program to another location without changing the registry/configuration.