5 ms·
All jokes are only funny when they are resembling to the truth but they are not when it's far from it. So this maybe funny five years ago. But it doesn't any mo
by devy 8y ago
All jokes are only funny when they are resembling to the truth but they are not when it's far from it. So this maybe funny five years ago. But it doesn't any more since Docker[1].
docker pull; docker run, you are golden. Even if you are going to customize the official image, it's much less cumbersome than that xkcd cartoon.
[1]: https://hub.docker.com/_/python/ https://hub.docker.com/_/python/
- fenwick67 8y agoOh look, we found one more arrow to add to the chart!
- devy 8y agoYou mean one more solution to add to the chart to solve that mess?
- cdancette 8y agohttps://xkcd.com/927/ https://xkcd.com/927/
- adtac 8y agoThat's what every solution aims to be at the start.
- your-nanny 8y agoOne noodle to rule them all.
- JustSomeNobody 8y agoEvery solution has drawbacks. What are some for the solution you propose?
- icebraining 8y agoSorry, can't run Docker on the Windows Server 2012 machines provided by the client. Or on the CentOS 6 machines provided by the other.
- devy 8y agoNot sure what your specific situation is, afaik it's possible. So your problem might not be pertaining to Docker Python. https://www.liquidweb.com/kb/how-to-install-docker-on-centos-6/ https://www.liquidweb.com/kb/how-to-install-docker-on-centos...
- icebraining 8y agoYes, but you'd have to run a 2.5+ years old - and unsupported - version of Docker (1.7.1).
- devy 8y agoWhat version of Python you'd be running? And Windows Server 2012 is 5 years old, no? If you are running a five years old OS, perhaps unsuported Docker version 1.7 (released 2015) might not be your only and most import concern right?
- icebraining 8y agoWe are running the latest Python 2 release, compiled from source. Windows Server 2012 will be supported until 2023, and CentOS 6 until 2020.
- rimunroe 8y agoI can assure you that this state of things is still pretty relevant to some of us.
- cossatot 8y agoIs this your comic, perhaps?
- rimunroe 8y agoNah, but I was helping the author clean up his Python environment on Friday, which I think prompted this comic. His environment isn't even the messiest I've seen. I helped an astronomer friend with theirs at one point, and it had something like six different "manage your whole Python workflow easily with just this tool!" things installed. I think what a lot of comments here miss is that while new tools come out that can help make things better, they don't suddenly fix people's existing installs. It seems weird that there isn't more documentation out there to help people get out of these kinds of messes.
- cossatot 8y agoNo disagreement from me on the sorry state of things.
- pwang 8y agoExactly right. There is an irreversible entropy to this: once a certain number of implementations exist, it becomes almost impossible to create a "new standard" that fixes them all, because it has to be backwards compatible with too many of them. As someone responsible for probably one of your astronomer friend's tools (Anaconda), I have to say that we can only do so much: the nature of Python itself is that we cannot ignore what the user puts into PYTHONPATH, PATH, etc. On Windows, at least, we do create shortcuts in the Start Menu to ensure that we get a well-defined command shell. But if the user forces things like PYTHONPATH, there's not much we can do to un-fsck the setup. Maybe it would be useful to have a python-safemode (or python-portable) binary that explicitly ignores all environment variables, configuration files, registry settings, dotfiles, etc. etc. and only looks at files that are next to it in the path....