Sorry Python but it is what it is.

you are viewing a single comment's thread
view the rest of the comments
[–] 25 points 2 years ago (1 child)

I don't think it's fair to blame pip for some ancient abandoned packages you tried to use.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] -3 points 2 years ago (1 child)

    The issues I had:

    • packages installing but not working due to missing dependencies
    • packages installing but not working due to broken dependencies (wrong lib version installed)
    • packages not building and failing with obscure errors
    • one package was abandoned and using Python 2.7

    If a 'pip install X' completes successfully but X doesn't work it's on pip. And when it fails it could tell you why. Cargo does.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 2 years ago*

    packages installing but not working due to missing dependencies

    This is the fault of the package author/maintainer

    packages installing but not working due to broken dependencies

    Sometimes the fault of the package author/maintainer. Sometimes this is the fault of a different package you're also trying to use in tandem. Ultimately this is a problem with the shared library approach python takes and it can be 'solved' by vendoring within your own package.

    packages not building and failing with obscure errors

    Assuming the package is good, this is a problem with your build system. It's like complaining a make file won't run because your system doesn't have gcc installed.

    one package was abandoned and using Python 2.7

    Unfortunately there's a ton of this kind of stuff. I suppose you can blame pypi for this, they should have some kind of warning for essentially abandoned projects.

  • source
  • parent