4 ms·

I've been writing Python forEVER and the one thing I fail to comprehend about it is how the dependency situation on Python only gets worse. It has somehow surpa

I've been writing Python forEVER and the one thing I fail to comprehend about it is how the dependency situation on Python only gets worse. It has somehow surpassed pre-nvm Node for being a total dependency clusterfuck. What are we using now? Pip? Pyenv? Pipenv? Poetry? Hatch? Conda? Once that's settled, there's invariable some library that has some native buildchain tooling requirement that isn't satisfied and the build process has shat all over my terminal. So now I have to hunt down whatever libraries gcc is complaining about. Christ, it should be against the law to release a programming language that doesn't have dependency management built-in.

mountainriver 4y ago
100% I switch between Go and Python a lot and even with Go mods detractions it’s still so much simpler to have everyone using one package manager built into the standard toolchain
orf 4y ago
Poetry is all you need.
BerislavLopac 4y ago
> What are we using now? > > Pip? Of course, for standard package installation. > Pyenv? Yes, if you need multiple Python versions available on the same system. > Pipenv? God no. https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-lot-delivers-very-little/ https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-l... > Poetry? Hatch? Yes, for local environment management and library dependency configuration. > Conda? Not really, unless you're doing data science and are heavily invested in the rest of Anaconda ecosystem. I don't really understand where the confusion is coming from - Python is used in a wide number of use cases and scenarios, and it is no surprise that there are many different tools in the box, each solving a different subset of problems. The packaging issue has been all but resolved in recent years, with the advent of wheels, pyproject.toml and a number of other standards. > So now I have to hunt down whatever libraries gcc is complaining about. Which has nothing to do with Python.

mountainriver 4y ago

100% I switch between Go and Python a lot and even with Go mods detractions it’s still so much simpler to have everyone using one package manager built into the standard toolchain

orf 4y ago

Poetry is all you need.

BerislavLopac 4y ago

> What are we using now? > > Pip? Of course, for standard package installation. > Pyenv? Yes, if you need multiple Python versions available on the same system. > Pipenv? God no. https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-lot-delivers-very-little/ https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-l... > Poetry? Hatch? Yes, for local environment management and library dependency configuration. > Conda? Not really, unless you're doing data science and are heavily invested in the rest of Anaconda ecosystem. I don't really understand where the confusion is coming from - Python is used in a wide number of use cases and scenarios, and it is no surprise that there are many different tools in the box, each solving a different subset of problems. The packaging issue has been all but resolved in recent years, with the advent of wheels, pyproject.toml and a number of other standards. > So now I have to hunt down whatever libraries gcc is complaining about. Which has nothing to do with Python.