4 ms·
That's what cool kids use today; just dump complete dependency tree of every project into random location on filesystem. That's not how Debian OS works though,
by inshadows 6y ago
That's what cool kids use today; just dump complete dependency tree of every project into random location on filesystem. That's not how Debian OS works though, and that's what author, a sysadmin, talks about very clearly. So I don't get why you propose exactly what he dismissed in the 2nd paragraph.
> and the environment our Python program runs in doesn't really have a home directory to use pip's --user option
- hprotagonist 6y agoI do all of this on debian, literally every day. from the perspective of a developer, debian makes absolutely idiotic decisions about how python is packaged and managed by apt, so i opt out completely!
- inshadows 6y agoReally? I do `apt-get install foo` and later I in a Python script I write `import foo`. This Python script can be put ANYWHERE on the system. I don't need to mess up with virtualenvs and I have one version across all scripts on the system that's regularly updated on system upgrades (after being tested by community in bleeding edge versions of the OS). To each his own I guess.
- hprotagonist 6y agoapt doesn't have my stack or its dependencies at proper versions, and cannot in general meet the version-locking of dependencies i and my dependencies require. And --system-site-packages is a baaaaad idea.