How can I deal with the case where I have a depend...
# generalb
brief-engine-92399
11/01/2025, 11:38 PMHow can I deal with the case where I have a dependency that forgot to add a build requirement to its build-requires, e.g., forgetting to add torch and expects --no-build-isolation alternatively?
(other than forking it and adding the dep to build-requires myself)
b
brief-scientist-13682
11/02/2025, 1:52 AMForking is exactly the right answer! You can use the fix immediately and push a PR async to help them - and everyone else in your situation - out.
brief-scientist-13682
11/02/2025, 1:52 AMJust use a VCS dep on your fork.
b
brief-engine-92399
11/02/2025, 1:54 AMThat's exactly what I'm doing 🙂 .
I think we're gonna need to vendor a lot of libs at this rate lol. Probably for the best anyway
brief-engine-92399
11/02/2025, 1:54 AMThanks
b
brief-scientist-13682
11/02/2025, 1:54 AMYour welcome. And there is no other way currently that I'm aware of.
😞 1
brief-scientist-13682
11/02/2025, 1:55 AMIts not much of a sad face though, at least in terms of perf usually. If you're already building an sdist, usually the clone vs download sdist tarball isn't a big latency factor compared to the build itself. You've already lost if you need to build.
b
brief-engine-92399
11/02/2025, 1:58 AMAh. Anyway, I looked into open prs in the repo I'm staring at and they explicitly want
--no-build-isolationb
brief-scientist-13682
11/02/2025, 1:59 AMOk, then the only solution I know of is you need to pre-build wheels and host.
brief-scientist-13682
11/02/2025, 1:59 AMLots of mid / big shops due this for a host of other reasons as a matter of policy / principle.
b
brief-engine-92399
11/02/2025, 2:00 AMWe used to do that too.
brief-engine-92399
11/02/2025, 2:00 AMWe dont need to anymore with this specific one for weird reasons (as I've hinted at in other threads). Pretty sure I can remove this
python_requirementb
brief-scientist-13682
11/02/2025, 2:01 AMK
6 Views