-
Notifications
You must be signed in to change notification settings - Fork 15
Make traker optional for LESS/NICE installation #40
Copy link
Copy link
Open
Description
Problem
traker is currently listed in the base requirements.txt. This makes first-time installation much heavier than necessary, because traker pulls in large PyTorch/CUDA wheels even when the user does not plan to run LESS or NICE.
In practice this causes installation failures for new users on slower or unstable networks. For example, uv pip install -r requirements.txt can fail while downloading nvidia-cublas through the traker -> torch -> cuda-toolkit dependency chain.
Why this is a usability issue
LESSandNICEare optional algorithms, not part of the minimal path to try DataFlex.- New users should be able to install the base package and run lighter selectors/mixers without downloading the full
trakerstack. - Current failures happen during installation, before users even understand which algorithms require extra dependencies.
Proposed minimal fix
- Remove
trakerfrom the baserequirements.txt. - Add optional extras in
pyproject.toml, for example.[traker],.[less], and.[nice]. - Lazy-load
trakerinsideless_selector.pyandnice_selector.py. - Raise a clear error message when a user selects
LESSorNICEwithout the optional dependency installed. - Update both
README.mdandREADME-zh.mdto document base installation vs optionalLESS/NICEinstallation, including a timeout hint foruv.
Expected outcome
- Base install becomes lighter and more reliable for first-time users.
- Advanced users can still install
LESSandNICEexplicitly. - Installation errors become actionable instead of failing deep inside the CUDA dependency chain.
I have prepared a small patch for this and will open a PR linked to this issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels