Sorry Python but it is what it is.

  • clearleaf@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    The problem is 2 and modules for 2 still tend to worm their way in somehow. I always use python3 -m pip because I never trust that “pip” alone is going to be python3 pip and I think that’s what the people who have lots of trouble with pip aren’t doing.

    • Fushuan [he/him]@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      It would be weird to have python2-pip installed if you don’t have python2 installed, pip should be python2-pip by default on most systems.

      I… Dunno, are you suggesting that sometimes pip2 is the default and that that somehow mixes 2 and 3 modules? Pip 2 should install into python 2’s directory and pip 3 to python 3’s. The only times I have had messy python environments is when I mix pipenv, conda and/or pip, and when people install into the main python with specific versioning, use a virtual env for God’s sake, that’s what npm does.

    • ArbiterXero@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Valid point.

      I force everything to 3 and don’t accept any 2.

      And in fairness, there were some moderate breaking changes 3.6-3.8