6 ms·

`pip` is a horribly broken way to install more than 1 Python package on a single Linux OS install and I sincerely wish the LLM people would move away from it be

`pip` is a horribly broken way to install more than 1 Python package on a single Linux OS install and I sincerely wish the LLM people would move away from it because I neither want to run every new project in a Docker image, nor do I want to start a new Nix project for every Python project I want to try out

RockRobotRock 3y ago
Have you heard of virtual environments?
- pmarreck 3y ago
  Have you ever googled "broken virtualenv"? Mine have broken numerous times, including the problem where updating the system breaks ALL of them. I know what you're going to say next- "You're a technologist, you know how to fix it." True, but I don't like wasted effort, even talented wasted effort is still wasted effort. Meanwhile, Nix stuff just works, and I will never use another package manager ever again (unless it is something that uses the core Nix idea, but makes it easier!) https://www.google.com/search?q=broken+virtualenv https://www.google.com/search?q=broken+virtualenv
  - RockRobotRock 3y ago
    I agree with you, Python packaging is in a rough state.
okwhateverdude 3y ago
Yeah, gotta setup miniconda to keep things manageable. Basically a generic virtual env manager that is trivial to use. This way you can ensure each one of these LLM projects that want different versions of different libs will get them without stepping on each other or polluting your system.
- pmarreck 3y ago
  I don't want to have to set up miniconda. I don't like Python, I am not part of the Python ecosystem, and I don't want to add a bunch of Python tools to my toolchain just to run a friggin' LLM project. I'm not a C coder either, but I don't complain about those projects because they're almost always "config; make; make install". I basically want something like that, but for Python. The nerd-tapdancing required here is ridiculous.

6 ms·

`pip` is a horribly broken way to install more than 1 Python package on a single Linux OS install and I sincerely wish the LLM people would move away from it be

by pmarreck 3y ago

RockRobotRock 3y ago
Have you heard of virtual environments?
- pmarreck 3y ago
  Have you ever googled "broken virtualenv"? Mine have broken numerous times, including the problem where updating the system breaks ALL of them. I know what you're going to say next- "You're a technologist, you know how to fix it." True, but I don't like wasted effort, even talented wasted effort is still wasted effort. Meanwhile, Nix stuff just works, and I will never use another package manager ever again (unless it is something that uses the core Nix idea, but makes it easier!) https://www.google.com/search?q=broken+virtualenv https://www.google.com/search?q=broken+virtualenv
  - RockRobotRock 3y ago
    I agree with you, Python packaging is in a rough state.
okwhateverdude 3y ago
Yeah, gotta setup miniconda to keep things manageable. Basically a generic virtual env manager that is trivial to use. This way you can ensure each one of these LLM projects that want different versions of different libs will get them without stepping on each other or polluting your system.
- pmarreck 3y ago
  I don't want to have to set up miniconda. I don't like Python, I am not part of the Python ecosystem, and I don't want to add a bunch of Python tools to my toolchain just to run a friggin' LLM project. I'm not a C coder either, but I don't complain about those projects because they're almost always "config; make; make install". I basically want something like that, but for Python. The nerd-tapdancing required here is ridiculous.