Creating env in custom folder with custom requirements.txt location

Bugs
,
1

Hello, thanks to the help of the community on my previous post I was able to implement a venv successfully. This, assuming I keep the env and the requirements.txt in the same location of the toe file.

As soon as I try and move the requirements.txt, I am unable to auto-create and auto-install my environment. My situation is the following.

FolderOne:
→ tdOne.toe
FolderTwo:
→ tdTwo.toe
PythonFolder:
→ requirements.txt
→ .env

I would like to auto-create and auto install everything in the “Python folder” which is at the same level as FolderOne and FolderTwo. This would then enable me to point at the same .env from both toes to avoid duplication.

However, whilst I can create the env in the correct location, I can’t point at a “requirements.txt” in a different location, and as soon as I move the env, TD is unable to autoinstall everything.

Is this a known bug? From the TD console I see that TD literally uses the wrong path, even though the yaml file is correct.

OS: Windows 11 Pro Version 10.0.26200 Build 26200
TouchDesigner Build: 2025.32280

2

In the context file you should be able to add additional requirement-files in the autoSetupReqs: [] key. So in your case it should be
autoSetupReqs: ["../PythonFolder/requirements.txt"]

But this might also be a bug or unclear behaviour. @JetXS should have some additional wisdom here.

3

Hi @plusplusone, I was hoping you would reply!

Unfortunately, I tried a bunch of things, both with relative and absolute paths, but nothing seems to work.

If you want I can provide a test zip to showcase the behaviour.

4

I think it’s better to post your full context file, TD version and any logs from the text port and a description of the expected behavior and how it suffers so @JetXS can give additional insight or add it to the bug queue.

5

Working setup

Folder structure
→ Folder One

  • tdOne.toe
  • TDPyEnvManagerContext.yaml
  • requirements.txt

→ globscripts
→ PythonFolder

yaml contents

active: true
mode: Python vEnv
envName: .venv
installPath: .
pythonVersion: '3.11.10'
autoSetup: true
autoSetupReqs:
- requirements.txt
extraPaths:
- C:\envTest\globscripts

Behaviour
On toe launch, the environment gets correctly creates in FolderOne, and pandas gets correctly installed as it’s the only library listed in requirements.txt. Moreover, printing “sys.path” from the Textport correctly lists both the extraPath and the env:

['C:\\envTest\\globscripts', 'C:\\envTest\\FolderOne\\.venv\\Lib\\site-packages', 'C:\\Program Files\\Derivative\\TouchDesigner.2025.32280\\bin\\python311.zip', 'C:\\Program Files\\Derivative\\TouchDesigner.2025.32280\\bin\\DLLs', 'C:\\Program Files\\Derivative\\TouchDesigner.2025.32280\\bin\\Lib', 'C:\\Program Files\\Derivative\\TouchDesigner.2025.32280\\bin', 'C:\\Program Files\\Derivative\\TouchDesigner.2025.32280\\bin\\Lib\\site-packages']

Broken setup

Folder structure
→ Folder One

  • tdOne.toe
  • TDPyEnvManagerContext.yaml

→ globscripts
→ PythonFolder

  • requirements.txt

yaml contents

active: true
mode: Python vEnv
envName: .venv
installPath:  ../PythonFolder
pythonVersion: '3.11.10'
autoSetup: true
autoSetupReqs:
- ../PythonFolder/requirements.txt
extraPaths:
- C:\envTest\globscripts

Behaviour
On toe launch, the environment gets wrongly created inside FolderOne instead of PythonFolder, but the requirements.txt file is found and thus the env is created correctly in the wrong place. The yaml file is overwritten with the installPath substituted to “.”.

Variants

  • Using the absolute path instead (C:\envTest\PythonFolder) creates the environement in the correct location but fails to install the libraries, and throws the following error on the Textport:
2026-06-04 14:52:34,206 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Python executable not found for requirements install: C:\envTest\FolderOne\.venv\Scripts\python.exe
2026-06-04 14:52:34,207 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Python executable not found at C:\envTest\FolderOne\.venv\Scripts\python.exe.
2026-06-04 14:52:34,207 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Environment C:\envTest\FolderOne\.venv could not be linked. Context is: {'active': False, 'mode': 'Python vEnv', 'envName': '.venv', 'installPath': 'C:\\envTest\\PythonFolder', 'envPath': 'C:\\envTest\\FolderOne\\.venv', 'executablePath': 'C:\\envTest\\FolderOne\\.venv\\Scripts\\python.exe', 'osPath': [], 'sysPath': [], 'pythonVersion': '3.11.10', 'autoSetup': True, 'autoSetupReqs': ['..\\PythonFolder\\requirements.txt'], 'extraPaths': ['C:\\envTest\\globscripts']}
2026-06-04 14:52:34,208 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Python executable not found at C:\envTest\FolderOne\.venv\Scripts\python.exe.
2026-06-04 14:52:34,208 - ERROR - TDAppLogger.TDPyEnvManagerHelper - Environment C:\envTest\FolderOne\.venv could not be linked. Context is: {'active': False, 'mode': 'Python vEnv', 'envName': '.venv', 'installPath': 'C:\\envTest\\PythonFolder', 'envPath': 'C:\\envTest\\FolderOne\\.venv', 'executablePath': 'C:\\envTest\\FolderOne\\.venv\\Scripts\\python.exe', 'osPath': [], 'sysPath': [], 'pythonVersion': '3.11.10', 'autoSetup': True, 'autoSetupReqs': ['..\\PythonFolder\\requirements.txt'], 'extraPaths': ['C:\\envTest\\globscripts']}
  • I tried making also the requirements path absolute, with the same outcome.
  • I tried making the envName a full path, but that overwrites the yaml completey to make the path local again
1 Like
7

I’ll have a look.

Thanks for the report,
Michel