3 ms·

That's what everybody uses `venv` for. Or `virtualenv` if you're stuck on old Python. But as a rule, `<=` dependencies mean there's either a disastrous fault w

• int_19h 1y ago
  Virtual environments don't solve the problem of two dependencies that you need having conflicting requirements.
  • o11c 1y ago
    That subproblem is fundamentally unfixable unless you're willing to allow incompatible objects to be passed around, which is a really bad idea. If your code does: o = foo_v1.get_obj() foo_v2.use_obj(o) then this is almost always undefined behavior, since the authors of `foo` will almost certainly not write their APIs to accept instances with different internals.
    • Dylan16807 1y ago
      With a more advanced system you can look at whether a package's use of foo is exposed in its API or completely internal, and then allow different isolated islands of packages to use different versions of foo.
• dheera 1y ago
  Venvs also suck because the user has to create and activate them. It would be nice if a foo.py file could just deal with all of that. A while ago I created this thing as a thought experiment. It likely doesn't work with more recent version of python though: https://news.ycombinator.com/item?id=24735303 https://news.ycombinator.com/item?id=24735303 It was partly in jest but I was not entirely un-serious; I think "dealing with dependencies" is quite possibly the biggest reason why Python isn't used to distribute end-user applications. It's a wonderful language but a really shitty import system. There are various attempts to make the experience better (pipx, poetry) but you still can't ship a .py file to someone, have them double click and run it. They still have to conda something, venv something, pipx something.
  • yjftsjthsd-h 1y ago
    I think uv does what you want: https://docs.astral.sh/uv/guides/scripts/#declaring-script-dependencies https://docs.astral.sh/uv/guides/scripts/#declaring-script-d...
• deleted 1y ago
  [deleted]