[Piglit] [PATCH] Revert "python: change she-bang to python2"

Ilia Mirkin imirkin at alum.mit.edu
Tue Jun 24 10:30:52 PDT 2014

On Tue, Jun 24, 2014 at 1:24 PM, Ian Romanick <idr at freedesktop.org> wrote:
> On 06/24/2014 10:08 AM, Ilia Mirkin wrote:
>> On Tue, Jun 24, 2014 at 1:04 PM, Ian Romanick <idr at freedesktop.org> wrote:
>>> On 06/24/2014 08:27 AM, Ilia Mirkin wrote:
>>>> On Tue, Jun 24, 2014 at 11:20 AM, Kenneth Graunke <kenneth at whitecape.org> wrote:
>>>>> For the record, I dislike that Arch has installed Python 3 as /usr/bin/python.
>>>>> It's incompatible and has caused no end of headaches for upstreams.  But,
>>>>> there's not a lot we can do about that.
>>>> Isn't there? Refuse to go along with the idiocy until Arch fixes it or
>>>> people stop using it...
>>> What you're suggesting is called "pissing in the wind."  Not generally
>>> producitve.  At some point you just have to get work done.
>> So that strategy works for Arch but not for us?
> Ask the question: Who is hurt by the stubborness of an Arch boycott?
> It certainly won't hurt Arch, and it has approximately epsilon
> probability of making them change.
> It certainly will hurt some piglit developers that encounter Arch systems.
> We're only hurting our own community... hence my original analogy.

If piglit as a project is the only one taking the stand? You're 100%
right. However if all software developers take this approach, then
Arch will definitely have to change (or have to start patching _tons_
of stuff). It has to start somehow. The attitude should be "it is
broken for python to not be python2.x", not "we should cater to
various incompatibilities introduced by odd distros". (Or perhaps you
disagree on that point, in which case, fine.)

And the piglit community is a fairly tech-savvy one, so if we throw in
the detection thing that yells at you for trying it with p3yk, they'll
be able to handle it.


More information about the Piglit mailing list