If I understand Dependencies for build backends, and debundling issues - #29 by ofek correctly, that’s changing soon for Hatch.
I think you’re alluding to them automatically generating a lock file and then continuing to use that file going forward while it exists regardless of whether it’s been checking into VCS?
Trying to standardize that has been brought up before and typically has been shot down (e.g. Providing a way to specify how to run tests (and docs?) ). I think the issue typically comes down to choosing a scope (API or just shell command), and then what to do for OS variances. But I’m a supporter for something like this, so I’m the wrong person to ask why we shouldn’t do it. ![]()