2 ms·
> I think the author would have better spent his time learning the basic usage of virtualenv/venv than writing this blog post. I don't. Virtualenv is a hack to
by IshKebab 6y ago
> I think the author would have better spent his time learning the basic usage of virtualenv/venv than writing this blog post.
I don't. Virtualenv is a hack to workaround the mess of Python paths that they won't actually fix. I'd put it in a similar bucket as Docker (hacking around the mess of binary software distribution on Linux).
I don't want to spend my time learning workarounds.
- gojomo 6y agoBut, it's a "hack workaround" that a professional consensus has converged upon. Pythonistas have developed supporting tools & help-texts, & many assume the use of silo'd virtual environments as 'basic hygiene' for serious work. The approach is also highly analogous to other "alternate virtual root" solutions across OSes/containers/user-customization schemes. So instead of that, you'd rather... make you own custom hack workarounds? That will be idiosyncratic to your installations/projects? That will hit unique errors/tradeoffs the standard convention has already worked around? That will be harder for others to understand? OK, to each their own!