I frequently find myself writing my own short command-line scripts in Python that help me with day-to-day tasks. It’s so easy to throw together …
  • RecallMadness@lemmy.nz
    2·
    2 days ago

    Or, you could package it as a Pex.

    • it would just need a compatible Python version
    • no additionalional packaging tools need to be installed by your users
    • all of the dependencies packaged together once. as they were built and tested against.
    • doesn’t need installing. Doesn’t install anything. Just run it.
    • doesn’t depend on pypi being accessible.
    • Voroxpete@sh.itjust.works
      4·
      2 days ago

      Correct me if I’m wrong, but I don’t think pipx can allow you to just put a shebang at the top of a script that automatically installs all the required dependencies the first time you run it?

      What I really like about this, unless I’m missing something, is that it basically lets you create Python scripts that run in exactly the same way as shell scripts. I work with a lot of people who have pretty good basic Linux knowledge, but are completely at a loss when it comes to python specific stuff. Being able to send them a script that they can just +x and run sounds like a huge hassle saver.

      • Daniel Quinn@lemmy.caEnglish
        2·
        2 days ago

        Nope, pipx definitely can’t do that, but the idea that running your yourscript.py --help will automatically trigger the downloading of dependencies and installing them somewhere isn’t really appealing. I’m sure I’m not the only person who’s got uv configured to install the virtualenv in the local .venv folder rather than buried into my home dir, so this would come with the added surprise that every time I invoke the script, I’d get a new set of dependencies installed wherever I happen to be.

        I mean, it’s neat that you can do this, but as a user I wouldn’t appreciate the surprise behaviour. pipx isn’t perfect, but at least it lets you manage things like updates.

        • Eager Eagle@lemmy.worldEnglish
          1·
          2 days ago

          I’m sure I’m not the only person who’s got uv configured to install the virtualenv in the local .venv folder

          That’s the default for projects. Script is a different run mode.

          every time I invoke the script, I’d get a new set of dependencies installed wherever I happen to be.

          Does that happen though? uv uses the cache location for these script dependencies, not your usual venv one. Where you call it from is not a factor.