From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SYDgj-0007M1-CC for garchives@archives.gentoo.org; Sat, 26 May 2012 09:53:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B1B39E057F; Sat, 26 May 2012 09:53:30 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 81FDBE057F for ; Sat, 26 May 2012 09:53:30 +0000 (UTC) Received: from pomiocik.lan (87-205-57-114.adsl.inetia.pl [87.205.57.114]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id A7632643ED; Sat, 26 May 2012 09:53:28 +0000 (UTC) Date: Sat, 26 May 2012 11:53:22 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Maxim Koltsov Cc: gentoo-python@lists.gentoo.org Subject: Re: [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass Message-ID: <20120526115322.0cbf1b41@pomiocik.lan> In-Reply-To: References: Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/.43kobQ.gCBdl77pw8AUV/5"; protocol="application/pgp-signature" X-Archives-Salt: b190aff7-1833-4f41-812a-993e5d096ac8 X-Archives-Hash: 172a4fbc60eaaa18dbd48210935e8844 --Sig_/.43kobQ.gCBdl77pw8AUV/5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 26 May 2012 13:32:30 +0400 Maxim Koltsov wrote: > I want to say that I personally don't want to use python-distutils-ng > in its current state and I know several active python ebuild writers > that are not Gentoo developers and they don't want to use it too. > First of all, how well is this eclass adapted to packages not using > distutils? Old eclass had set of convenient functions > (python_execute_function, python_generate_wrapper_scripts, > python_conver_shebangs). I see some functions like these ones in new > eclass, but can they serve as good replace and is their API public and > stable? We're planning on splitting some basic 'python' eclass out of it. Just someone needs to do that, or I'll when I'll have more time and a good plan. > Then, we think that this ruby-ng style approach with PYTHON_TARGETS is > a bit uncomfortable for end users and developers. This is going to be > pain for all users if eclass gets used widely. Eclass allows developer > not to set PYTHON_COMPAT and populate it with all available values =E2=80= =94 > well, it's nice. I think we can disable that early if new Python versions are likely to introduce breakages. > But imagine that Python 3.3 arrives. All ebuilds > using new eclass will get new IUSE and therefore will be rebuilt > during emerge --update --newuse world. That's hardly sensible. It's > awful to rebuild packages which might be very 'heavy' just for > nothing. We don't support '--newuse' in Gentoo. People who do that are on their own. We have enough problems to care about in our workflow. > On the other hand, if developers are forced to set PYTHON_COMPAT, this > will result in great delays in getting new python support to Gentoo. > You can say that ruby-ng has the same behavior and nobody complains. > But python is not ruby. Ruby 1.8 to 1.9 transitition was connected > with a lot of incompabilities, so one could not assume that ruby-1.8 > package will work on 1.9. Python 3.2 to 3.3 transitition should be > harmless and almost all packages will require no changes. So some > implicit mechanism of doing this must be implemented. I guess that 3.2->3.3 would include having python3_3 masked for a longer while to test it. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/.43kobQ.gCBdl77pw8AUV/5 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAk/AqBIACgkQfXuS5UK5QB3i4AQApNHhbNUTbccHS3EwbiWMFC0C RnB9oWUMQwD7Ows/9NUc1Iew3/J3p6QuUaEBZfeWdspvly8pyPQFrUogxgjX/34I lvDr9XaJNJq71BzejYS/1IF6SAzdRPOgBpsnx0ox7hN0eZV8907p1YyW0U9P2RVa IPdTyPKms+86J/pVQ5o= =7KOD -----END PGP SIGNATURE----- --Sig_/.43kobQ.gCBdl77pw8AUV/5--