Python Templates Should Include Standard Exclusions in rsync Tasks

Feature Request Draft

Title: Python Templates Should Include Standard Exclusions in rsync Tasks

Description:

The current Python project templates in the Torizon IDE Extension don’t include standard Python exclusions in rsync tasks by default. This causes unnecessary files like .venv, __pycache__, and .pyc files to be synced to the target device during debugging, which:

  • Significantly slows down deployment

  • Wastes bandwidth and storage

  • Can cause compatibility issues (e.g., venv from x86 host synced to ARM64 target)

Proposed Solution:

Update the default Python template’s rsync tasks (e.g., rsync-torizon-generic) to include standard Python exclusions:

json

"args": [

"-P",

"-av",

"--exclude=.venv",

"--exclude=**/__pycache__",

"--exclude=*.pyc",

"--exclude=.pytest_cache",

"--exclude=.tox",

"-e",

"ssh -p ${config:torizon_debug_ssh_port} -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null",

"${workspaceFolder}/your-app",

"${config:torizon_run_as}@${config:torizon_ip}:${config:torizon_app_root}/"

]

This aligns with standard Python .gitignore practices and improves developer experience out-of-the-box.

Environment:

  • Torizon OS 7.3

  • Torizon IDE Extension (current stable/pre-release)

  • Python projects


You can submit this to:

Greetings @jzylkin2,

I could forward this request to our team. But, keep in mind this will then be subject to our internal prioritization. This means it could be quite some time before our team decides to work on this, if they do decide to work on it.

Alternatively, you could make your own pull request (PR) with the suggested changed to the Python template to our repository here: GitHub - torizon/vscode-torizon-templates: VS Code Torizon Integrated Development Environment Templates · GitHub

This contains the source for the Torizon IDE Extension templates. We accept outside contributions on this. Of course our team will still need to review the contribution, but it would be a lot quicker if you would like to see this change sooner rather than later. Especially since it seems like you already have an idea of the change to implement.

All that said, would you like to open your own PR, or do you want me to report this request internally?

Best Regards,
Jeremias