From owner-freebsd-python@FreeBSD.ORG Wed Jan 23 18:09:11 2013 Return-Path: Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 44DFBE65 for ; Wed, 23 Jan 2013 18:09:11 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward3h.mail.yandex.net (forward3h.mail.yandex.net [IPv6:2a02:6b8:0:f05::3]) by mx1.freebsd.org (Postfix) with ESMTP id E69473EF for ; Wed, 23 Jan 2013 18:09:10 +0000 (UTC) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward3h.mail.yandex.net (Yandex) with ESMTP id 924A3136211D for ; Wed, 23 Jan 2013 22:09:08 +0400 (MSK) Received: from smtp1h.mail.yandex.net (localhost [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id 6E9681340123 for ; Wed, 23 Jan 2013 22:09:08 +0400 (MSK) Received: from unknown (unknown [178.76.224.133]) by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 97FCf60e-98FCD9K7; Wed, 23 Jan 2013 22:09:08 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1358964548; bh=ungzlZ3e9+ZMzBPWN39IZR1HLm4s0ZBPs5XvSq4PLMg=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Whs/TlCDEg4xmQf9e00qFmBaDGQpuVb5aGkYmyaJkVg7gbr3mggfH40VyRLOgXYL/ nmlJQHSicRs3DH5A6urqK3bOaDoyIuX6WcD91g1r0LTc4Bw6bm+LUc/g+wdrzwfFba 4bISYaheNXgCAKO/KGjRy4ZLs7YWvd5Tka67mXpg= Message-ID: <5100273E.6010300@yandex.ru> Date: Wed, 23 Jan 2013 22:09:02 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130114 Thunderbird/17.0.2 MIME-Version: 1.0 To: python@FreeBSD.org Subject: Re: bsd.python.mk: python3 plist shim References: <50FFD7C0.9060208@yandex.ru> <20130123165053.GA1978@medusa.sysfault.org> In-Reply-To: <20130123165053.GA1978@medusa.sysfault.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 18:09:11 -0000 Marcus von Appen wrote on 23.01.2013 20:50: > Hi, > > On, Wed Jan 23, 2013, Ruslan Makhmatkhanov wrote: > >> >> Hello, >> >> I'm planning to apply this patch to Mk/bsd.python.mk soon. It's an >> nivit's solution from devel/py-virtualenv for changes, introduced in PEP >> 3147 [1]. It will not affect default packages build, because packages >> are not yet building for python3 on cluster, but it will affect python >> ports, built with python3, that already has fix like that applied >> locally. I tested it with dozen of ports and everything seems fine. >> Local fixes will be removed right after this change. Please tell me if >> there is any objections or suggestions on this. Thanks. > > [...] > > I still do not get what the patch should exactly do and I am too lazy to > refresh my awk skills and try it out myself. If that patch is just about > the [INSERT cpython-correct-XX].pyc stuff, there is no need for it in my > opinion. > Can you please provide details on what the patch does? > > Cheers > Marcus Yes, it does just that by adding __pycache__ directories with compiled and optimized bytecode into pkg-plist. This allows us to make packages for python 3.2+ successfully. I can't explain more than that, because I treat that as some magic sequence for fixing py3 packages and that already applied locally in many ports, so it's time to just stop duplicating this pattern over the tree. Why do you think this isn't needed? Do you prefer patching the python internals to get the 2.x behavior or what? -- Regards, Ruslan Tinderboxing kills... the drives.