From owner-freebsd-python@freebsd.org Sun Nov 15 03:04:33 2015 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACE17A28E82 for ; Sun, 15 Nov 2015 03:04:33 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 374BA1F26; Sun, 15 Nov 2015 03:04:33 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by pacej9 with SMTP id ej9so31880342pac.2; Sat, 14 Nov 2015 19:04:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=sikUNNdJ/CulkvzBAIoouwkzblTRPi+pUIpk/hvHivk=; b=JqghVWWk5xQDyE31W9WqtOty9/JyupzXuxTw7C4taS5AJIeguI393svrS3j005oZ99 w8clY3kCIDKCofmPmFjKMm1pXVdANWEfdhd/8Wl87ugQulFb0/SMitOJf7u4nRZNYYTW Z73FGdeZ8tG8Sw2Sq4uCRUArpYcahWUICsRrxQeg5w/OTDoeewtHbcLsm3q7ZY1Zpx3p 0j99G+5TscHxDFpzju+2m89gqUZ2ryRAA/phnAI4m9TXF+5JbBQZdE2Fu2QouwvT0E5L XEoGpP0P5G2BQlIEHpRxkhSDqDZg5rbMZZa6OKcDqvw6YaChUnmcPnp7EPp2wOBD0qP8 3Xfw== X-Received: by 10.66.219.228 with SMTP id pr4mr43005491pac.99.1447556672755; Sat, 14 Nov 2015 19:04:32 -0800 (PST) Received: from ?IPv6:2001:44b8:31ae:7b01:a6:2228:3a9d:93b2? (2001-44b8-31ae-7b01-00a6-2228-3a9d-93b2.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:a6:2228:3a9d:93b2]) by smtp.gmail.com with ESMTPSA id qk7sm28226376pbb.80.2015.11.14.19.04.30 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 Nov 2015 19:04:32 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Version specified ports for separated standard Python modules References: To: Li-Wen Hsu , FreeBSD Python Team From: Kubilay Kocak X-Enigmail-Draft-Status: N1110 Message-ID: <5647F63B.6000303@FreeBSD.org> Date: Sun, 15 Nov 2015 14:04:27 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 03:04:33 -0000 On 15/11/2015 7:30 AM, Li-Wen Hsu wrote: > Hi, > > Just read this thread: > https://lists.freebsd.org/pipermail/freebsd-python/2015-November/009061.html > > This inspire me that we probably can create ports for those separated > standard Python modules, for each supported Python versions in the > tree. That is, adding databases/py3[2-5]-sqlite3, also for > databases/py-gdbm and x11-toolkits/py-tkinter. Adding these gives us > packages and this benefits pkg users, saving their time and space to > build from scratch. I also suggest these ports maintained by python@. > How do the people on this list think? These ports should be > straightforward, just slaves port with USES=python:X.Y . If no one > objects, I can add them. This might be the way to go until we have Python 3.x packages built by default. It would be nice to be *removing* the remaining py3- ports from the tree, not adding more, but in this case I'm not sure there's a better short term solution to address the missing functionality out of the box. > BTW, a thing surprises me is that we don't have a pkg-message which > hints users to install separated standard Python modules since > python34. Does anybody knows why? I haven't touched lang/pytohn* for > a while. I also found that python34 is directly added, not through > `svn cp` from python33 (well, python33 itself is also not...) If the pkg-message is inconsistent now, I'll fix it. Note this only solves the problem for ports users, not package users. python34 was directly added because it was built from scratch, leaving as much if not all of the old legacy behind. The initial commit log has more detail: https://svnweb.freebsd.org/ports?view=revision&revision=350610 > And, for the python-version-specified ports, I found now we have: > > devel/py-setuptools > devel/py-setuptools27 > devel/py-setuptools32 > devel/py-setuptools33 > devel/py-setuptools34 > devel/py-setuptools35 > > These give us following packages: > > py27-setuptools-17.0 > py27-setuptools27-17.0 > py32-setuptools32-17.0 > py33-setuptools33-17.0 > py34-setuptools34-17.0 > py35-setuptools35-17.0 > > I remember in the past, we add python-version-specified port using > pyXY-foo format. For example, we have See original commit and the issue it resolved: https://svnweb.freebsd.org/ports?view=revision&revision=347268 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187091 It's not pretty, but it's (still, I believe) needed, at least for now. > devel/py-dbus > devel/py3-dbus > > in ports, which generate > > py27-dbus-1.2.0_1 > py34-dbus-1.2.0_1 > > packages, so I think that the version suffix in port name is not > really needed. Or will trimming that make some other conflicts? > > Any idea? >