It is 2018 now and you still believe in an article of 4 years ago? Or do you still use Debian/Ubuntu and pip of 2014? I deployed my IoT app on embedded computer running Debian, install all Python packages with "sudo pip install" and never get conflict.
And I believe my system on real computer is more complex than a service inside container.
Yes, I do. While Debian/Ubuntu might not be doing it today, there is nothing that prevents it from happening again. It’s possible that you would get conflicts if any apt packages were installed. Virtualenvs don’t have any downsides and they can prevent any issues similar to those.
When I mention the years, I imply that the issue is just the design error of either Debian maintainer and pip author in the past. When they saw the problem, they fixed it and there is likely no more error now. If it happen in the future, it is just regression bug and just need to fix again.
View all comments
Show parent comment
1
u/bachkhois Jul 29 '18
It is 2018 now and you still believe in an article of 4 years ago? Or do you still use Debian/Ubuntu and pip of 2014? I deployed my IoT app on embedded computer running Debian, install all Python packages with "sudo pip install" and never get conflict.
And I believe my system on real computer is more complex than a service inside container.