3 ms·
Do this on a brand new MacBook (or for a bigger challenge, try it on a MacBook that already has a bunch of Python development tools installed). Count how many G
by TechBro8615 5y ago
Do this on a brand new MacBook (or for a bigger challenge, try it on a MacBook that already has a bunch of Python development tools installed). Count how many Google searches you need to make before you have a reproducible and isolated development environment you can share with a junior teammate.
- mlnj 5y agoAs someone who is fairly new to Python and have lost hundreds of hours on different project in this exact same situation. I've found Dockerized development containers (VS Code Remote Containers) to be a very good solution. Nothing leaks out. Everything is reproducible. But then again I do only web stuff.
- Brian_K_White 5y agoNeeding a container (outside of a system publishing reference builds) is evidense of a problem. The fact that a container is easy today just enables and hides the fact that it's a bit ridiculous to need one for half of the things we now use them for. Same for snap, flatpack, appimage, etc. Rather than have a handle on my surface and interface with the os, I'll just bundle an os with my calculator app. All because they're using a newer version of some library that maybe has an extra param on one function to automatically zero-pad or something. And "they" isn't necessarily the developer of the calculator app but could be the developers of any of the hundreds of dependencies. We all know all the excuses how we got here. We all know how each individual step along the way has it's excuse. Yet, it's not a great place we got to.
- gtf21 5y agoEvery time we have to have someone fix one of our relatively few python projects I rue the day I wrote them in python -- it often takes hours just to get it so the code runs on their machine.