FIXED: [2025.32050] EnvHelper AutoSetup not working

Bugs
1

It seems that the autosetup is not working correctly.
When starting TD for the first time with the following Context.json

{
    "active": true,
    "mode": "Python vEnv",
    "envName": "project_name_vEnv",
    "installPath": ".",
    "pythonVersion": "3.11",
    "pythonVersionNoDot": "311",
    "autoSetup": true
}

I get the following error. The folder for the venv gets created.

2026-01-15 09:14:01,534 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Python executable not found at C:\Users\Wieland PlusPlusOne\Documents\GitHub\Kundenprojekte\***\***\***_vEnv\Scripts\python.exe.
2026-01-15 09:14:01,535 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Environment C:\Users\Wieland PlusPlusOne\Documents\GitHub\Kundenprojekte\***\***\***_vEnv could not be linked. Context is: {'active': False, 'mode': 'Python vEnv', 'envName': '***_vEnv', 'installPath': 'C:\\Users\\Wieland PlusPlusOne\\Documents\\GitHub\\Kundenprojekte\\***\\***', 'envPath': 'C:\\Users\\Wieland PlusPlusOne\\Documents\\GitHub\\Kundenprojekte\\***\\***\\***_vEnv', 'executablePath': 'C:\\Users\\Wieland PlusPlusOne\\Documents\\GitHub\\Kundenprojekte\\***\\***\\***_vEnv\\Scripts\\python.exe', 'osPath': [], 'sysPath': [], 'pythonVersion': '3.11', 'pythonVersionNoDot': '311', 'autoSetup': True}

Running the setup prcedure by hand from inside TD does work as intendet.

Edit: it also seems that the install path will be replaced with the abspath version of it which makes it not useable for sharing via git.

2

Hi @plusplusone

I think the issue is that this version was not very friendly with the relative path in the installPath key.

Make it absolute and that should work I think.

Since things changed quite a bit in the version awaiting release, this should be much more reliable and support relative paths properly.

Best,
Michel

1 Like
3

A lot of improvements around relative vs absolute paths behavior were introduced, among other features in public build 2025.32280+.

Best,
Michel