[ please don't mail both me privately and the list with two separate mails: it's enough to choose one :-) ]
On Thu, Nov 25, 2010 at 02:06:21PM +0100, Olivier Guéry wrote: > Can you plan to adapt this to arch linux and the python2/3 mess ? > The configure script can’t find my pygtk module, but it’s here ! Sorry, but I really can't help that. I'm far from being a Python guru, but AFAICT [1,2] the conventions I've followed in the code are correct wrt what is recommended upstream, i.e. I expect that the "python" executable in $PATH is a 2.x Python. As Python 3.x really is a different language, applications using that should rely on the "python3" executable name. More specifically to your issue, the problem comes from the autoconf macro I use [3] which make a similar assumption. Even if I consider arch linux choice to be technically wrong, I'm ready to accept patches (from others) that makes life easier on arch linux, as long as they don't break upstream and other distros (reasonable) assumptions. Cheers. [1] http://docs.python.org/release/2.7/tutorial/interpreter.html#executable-python-scripts [2] http://docs.python.org/release/3.0/tutorial/interpreter.html#executable-python-scripts [3] http://www.gnu.org/software/autoconf-archive/ax_python_module.html -- Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7 z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/ Quando anche i santi ti voltano le spalle, | . |. I've fans everywhere ti resta John Fante -- V. Capossela .......| ..: |.......... -- C. Adams -- To unsubscribe, send mail to [email protected].
