From owner-freebsd-python@FreeBSD.ORG Tue Jun 5 17:43:20 2012 Return-Path: Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49538106564A; Tue, 5 Jun 2012 17:43:20 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward3.mail.yandex.net (forward3.mail.yandex.net [IPv6:2a02:6b8:0:602::3]) by mx1.freebsd.org (Postfix) with ESMTP id ACBC88FC18; Tue, 5 Jun 2012 17:43:19 +0000 (UTC) Received: from smtp4.mail.yandex.net (smtp4.mail.yandex.net [77.88.46.104]) by forward3.mail.yandex.net (Yandex) with ESMTP id 1DC63B41390; Tue, 5 Jun 2012 21:43:18 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1338918198; bh=WV4oS8lRLacjRZUBMwNU2kVr7LOpp47R0xHmh+NtOaQ=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=VvhToAV+2Elqe6ui93KbmiFzDI/x1Z01s7wg2phlZB+T5lAyxYx93CgVwXDCM6Sjp JLrGzEetzkPt7PSgxUkj2L4Y0QYA35EE9Eqtp/kb2Cs0ct+2kPZWU575XvSuZNoofd nzWLBgpdbVnfZ8dvUHrr1JAQ1MlnrhlMg3ASoI9Q= Received: from smtp4.mail.yandex.net (localhost [127.0.0.1]) by smtp4.mail.yandex.net (Yandex) with ESMTP id DEF0F5C04F2; Tue, 5 Jun 2012 21:43:17 +0400 (MSK) Received: from unknown (unknown [178.76.224.133]) by smtp4.mail.yandex.net (nwsmtp/Yandex) with ESMTP id hHHipRqj-hHH8lDSR; Tue, 5 Jun 2012 21:43:17 +0400 X-Yandex-Rcpt-Suid: jhein@symmetricom.com X-Yandex-Rcpt-Suid: bapt@FreeBSD.org X-Yandex-Rcpt-Suid: python@FreeBSD.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1338918197; bh=WV4oS8lRLacjRZUBMwNU2kVr7LOpp47R0xHmh+NtOaQ=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=FXHJ6Ac1DGCuYV0m1gkSM461j11jd4/h5d3f8HA/qKvO98mLpWRpcHCNOwm5HslHc 2ELdNmhSIYqSOjfHix2DADkS859FGjvtMmcRxXgTDFf2KhhSSU6eZhmWdsWtZzDDQO IrulVvzBVwf2U93FVVQCblR2fPjrHIZAJH+zK+9A= Message-ID: <4FCE4514.1020901@yandex.ru> Date: Tue, 05 Jun 2012 21:42:44 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120504 Thunderbird/12.0.1 MIME-Version: 1.0 To: John Hein References: <20120605120755.GA71005@ithaqua.etoilebsd.net> <4FCDF80F.3070304@yandex.ru> <20430.15706.546137.332233@gromit.timing.com> In-Reply-To: <20430.15706.546137.332233@gromit.timing.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Baptiste Daroussin , python@FreeBSD.org Subject: Re: Python conflicting with other python when installed from packages X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 17:43:20 -0000 John Hein wrote on 05.06.2012 21:09: > Ruslan Mahmatkhanov wrote at 16:14 +0400 on Jun 5, 2012: > > Baptiste Daroussin wrote on 05.06.2012 16:07: > > > Hi, > > > > > > With pkgng build on pointyhat I discovered that all the python packages when > > > built on pointyhat, tinderbox or even poudriere all conflicts which each other > > > meaning you can't install multiple python version in parallel without > > > overwritting files with old package system and pkgng just forbid you to install > > > the second package to avoid overwritting the file. > > > > > > The thing is that they are conflicting only for the bin/2to3 file. It would be > > > nice if this file could be for example prefixed with the release of python like: > > > > > > bin/py27-2to3 or something like that. I'm aware that when just installing from > > > ports only the first version of python installed got it, but if you are thinking > > > in package only world it can't works that way. > > > > > > regards, > > > Bapt > > > > Packages that using 2to3 to convert their code on install to be python3 > > compatible looking exactly for `2to3' executable. So such a modification > > would require modifying all the setup.py's according the python version > > user has installed as default. It's just a though. I didn't see how to > > resolve this correctly. > > One way: pull out 2to3 to its own separate port and have those > ports that need it specify the dependency. And, no, I don't > have patches. Well, then we'll get separate 2to3 ports that is conflicting :). I'm not sure that 2to3 is the same in all python distributions. -- Regards, Ruslan Tinderboxing kills... the drives.