Sorry Python but it is what it is.

  • rothaine@beehaw.org
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    1 year ago

    More like rtfms. I really didn’t feel like learning 20 different tools for repos my team didn’t touch very often.

    • CapeWearingAeroplane@sopuli.xyz
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I really don’t see the hassle… just pick one (e.g. pip/venv) and learn it in like half a day. It took college student me literally a couple hours to figure out how I could distribute a package to my peers that included compiled C++ code using pypi. The hardest part was figuring out how to cross compile the C++ lib. If you think it’s that hard to understand I really don’t know what to tell you…

      • rothaine@beehaw.org
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        Sure, for a new project. But when inheriting code I’m not in a position to pick.

        The point is that the state of python package managers is a hot fucking mess compared to npm. Claiming that “npm is just as bad” (or worse) honestly seems ridiculous to me.

        (And isn’t pip/venv the one the requirements.txt one? Completely flat, no way to discern the difference between direct dependencies and sub-dependencies? No hashes? Sucks when it’s time for updating? Yeah no thanks, I’d like a proper lock file. Which is probably why there are a dozen other tools.)