Hacker News Reader

> If it’s using a virtual environment, then they can pierce the abstraction by inheriting system packages

Which defeats the purpose of doing the build in a virtualenv, which is to avoid any possible collision with or contamination by other stuff that's installed on the system by using a fresh copy of everything.

View on HN

They’re already defeating the point of Python packaging in multifarious ways here. The entire reason uv and uv-build exist is because we have mature, smooth mechanisms for not rebuilding the world.

uv and uv-build are not equivalent to "Python packaging". Perhaps you would like them to be, but they're not.

I don’t know what “equivalent to” would mean here.

Speaking as someone who has written many Python packaging PEPs and who has maintained (and continues to maintain) PyPA tooling that you almost certainly use: uv and uv-build are as much a part of Python packaging as anything else that interfaces with the standards.

Reply on news.ycombinator.com