4 ms·
Python/Ruby/Node all suffer from this - the OS stubbornly thinks it knows what's best. Here's what I do. 1. Ignore the OS when developing - let it manage its o
by PopsiclePete 9y ago
Python/Ruby/Node all suffer from this - the OS stubbornly thinks it knows what's best. Here's what I do.
1. Ignore the OS when developing - let it manage its own dependencies for its own Python - fine. I use pyenv/rbenv/nvm to install my own dev. version of <language> and use isolated virtual environments for developing.
2. Deploy using Docker - again - ignoring whatever the OS has installed.
- viraptor 9y agoThat's kind of by design. You're supposed to develop with virtualenv. Then, if someone packages your app for inclusion into the distro, it's on them to package the compatible dependencies and your app. (I mean, it would be nice if the devs helped here, but that's what distribution maintainers are for) Not sure why you need docker though. It's fairly easy to distribute python libraries in a simple tarball.
- brianwawok 9y agoIf you want to do something like kubernetes you need to slap your python tar into a docker image.
- viraptor 9y agoNot sure I understand your point. Kubernetes is a service for managing containers. If you want kubernetes, of course you'll need containers of some sort. But not all apps need multi-host orchestration.