<br><br><div class="gmail_quote">On Thu, Nov 4, 2010 at 05:44, Allan McRae <span dir="ltr"><<a href="mailto:allan@archlinux.org">allan@archlinux.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
According to #python, we are all idiots.... <br></blockquote><div><br></div><div>To clarify (but I dont speak for the rest of #python, just myself), I think the move was premature, but I don't use Arch and I don't know what typical Arch users expect. The reason I think it's premature is that 'python2' just doesn't work everywhere, and I would have gone for a transitionary period where '/usr/bin/python' is something that screams loudly that it shouldn't be used before it executes 'python2'. That would've allowed for more time to fix things that use the wrong shebang line, or tools that use 'python' instead of letting distutils set it for them. I hope that's something other distributions will consider before changing the meaning of /usr/bin/python.</div>
<div><br></div><div>As for #python, well, we got this storm of people utterly confused about how their stuff doesn't work anymore, and putting the blame in the wrong place. I don't think a distribution should ever cause that (even though many do in lesser ways) -- but as I said, I don't use Arch so maybe I don't understand the purpose of it. The complaints seem to have died down now (though possibly because of the 'no arch' topic :)</div>
<div><br></div></div>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!<br>