News for hackers. Stuff that matters.
Re:Mongrel2 Says, "Goodbye Python" by gfunk911 on Tuesday September 21, 2010 @10:31AM (#1712707)
If the question is "Do a significant number of users run into problems with a piece of software," then the consensus is absolutely relevant.
Re:Mongrel2 Says, "Goodbye Python" by dschobel on Tuesday September 21, 2010 @10:36AM (#1712718)
The question isn't whether there is a problem but whether there is a solution. The virtualenv/pip people seem to think so.
Re:Mongrel2 Says, "Goodbye Python" by masklinn on Tuesday September 21, 2010 @12:02PM (#1713073)
> The virtualenv/pip people seem to think so.

No. Unless those people are morons, but the guys who actually code them know they're tools for python developers, and maybe for sysadmins of python solutions. Pip and virtualenv for software using Python as a config file format? not a good idea.

Re:Mongrel2 Says, "Goodbye Python" by zedshaw on Tuesday September 21, 2010 @01:15PM (#1713331)
Yes, pip/virtualenv works for installing things like Django.

It totally fails for something like m2sh which has to live in the system PATH so that you can run it from wherever you have your configs.

But you know, I wonder if the various distros could sort of invert this and they start using pip/virtualenv instead of everyone else working around them?

Re:Mongrel2 Says, "Goodbye Python" by jacobolus on Tuesday September 21, 2010 @02:49PM (#1713645)
The distros should be shipping two versions of python (if they need), walling their required old version off somewhere but actively and explicitly including a newer one higher up in the $PATH so that people don’t have to mess with the “system”. The problem is the combination of “system”, “third-party tools”, and “users” trying to use the same python with completely different upgrade timelines. If all of these distros included by default a recent-ish version, and their package managers made updating that one a snap, then third-party tools could stop trying to use system python for anything at all, and users could forget that the “system” python existed.

Unfortunately, since the problematic old python versions are on existing old distro versions, it’s not clear that there’s any easy way to fix this problem.