3 ms·
It's not clear cut like that. Sometimes your application will depend on a particular release of lxml or PIL, while the base system is already providing one (bec
by hcarvalhoalves 13y ago
It's not clear cut like that. Sometimes your application will depend on a particular release of lxml or PIL, while the base system is already providing one (because it's a dependency of something else). Or sometimes you can't install python packages that require compiling on your server because it doesn't have gcc and family installed (a common security practice). That's when apt/python packaging starts falling apart.
- fingerprinter 13y agoI have to say, I've not had the issue where I don't have nearly full control of a server. I do imagine this would provide many different challenges overall. Does PIL need to be compiled when you use it via Pip (I'm not familiar with PIL, tbh)? Can you just install those via pip and be done with it? So far using virtualenv + pip, I've not encountered a system library vs project dependency clash...but maybe I've just been lucky.