From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id BD75F138350 for ; Tue, 14 Jan 2020 06:45:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7A910E08AD; Tue, 14 Jan 2020 06:45:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9919AE089B for ; Tue, 14 Jan 2020 06:45:49 +0000 (UTC) Received: from [192.168.1.13] (c-73-173-172-109.hsd1.va.comcast.net [73.173.172.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: kumba) by smtp.gentoo.org (Postfix) with ESMTPSA id D6FB434E06D for ; Tue, 14 Jan 2020 06:45:47 +0000 (UTC) Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade To: gentoo-dev@lists.gentoo.org References: <15005ba1-1a1b-5d71-dbe3-7834b79ee733@gentoo.org> From: Joshua Kinard Openpgp: preference=signencrypt Message-ID: <2b1f4387-7464-a6f6-2820-7a32512136da@gentoo.org> Date: Tue, 14 Jan 2020 01:45:45 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: 96aaa3af-8de0-4b1f-8bad-178ef11feb16 X-Archives-Hash: e3a76be686b8c344bd33935ef086f5d0 On 1/13/2020 01:52, Michał Górny wrote: > On Sun, 2020-01-12 at 17:07 -0500, Joshua Kinard wrote: [snip] > Joshua, > > I understand that you don't do much Python ebuild work, or probably > Python development in general. I understand that you may feel like you > need more time with Python 2. But before sending such mails, please try > to put yourself in our skin. Actually, I've done a lot of general Python development over the last few years outside of Gentoo on work-related stuff. And I've had to convert those projects from Py2 to Py3, as well. In fact when faced with the decision of maintaining Py2 support alongside Py3, I cut my losses and ran, and dropped Py2 support in a new version. Wasn't worth the effort to maintain both with the limited development time I had. So I'm not walking into this conversation a happy idiot just saying random things to see what kind of fun I can cause. There are things I will absolutely miss in Python2 (goodbye, ASCII strings). But there are also things that I like about Python 3 (hello, lru_cache). So I've been there, in the proverbial trenches, and know of the pain fellow pythonistas have gone through over the last few years. That said, strictly on the ebuild-side of things, yes, I have not dabbled in that too much. But I do have some understanding of what you are going through. > Now imagine someone who doesn't really know much about maintaining > Python in Gentoo and problems related to Python 2 sunrising, grabs one > site about Python releases and tells me what to do without knowing > the wider context. Wouldn't you feel angry? Demotivated? Depressed > even? Actually, I wouldn't feel any of those at all. I'd probably laugh at it, in fact. Why laugh? Because in that context, I would have knowledge and understanding of the wider issue, while the poor sod who just proposed that crazy idea would not. And my laughter would be more at myself, because knowing the terrible truth kindles in me a desire to return to that time when I, too, was ignorant and happy and free. But the chains of knowledge bind me to a much more grim fate. > I mean, forgive my expression but we're deep in shit. As you've noticed > yourself, emerge spews few pages of 'I can't upgrade setuptools' because > of humongous number of packages that still need Python 2-capable > version. Sure, we could put some effort into making it still work with > Python 2, then start collecting more and more patches to various > packages just to keep things working. But then, 3-6-12 months from now > it will no longer be feasible, the cesspool will overflow and we'll be > even deeper in shit that we're today. > > If people started removing Python 2 from Gentoo years ago, like upstream > suggested, today things would be much better. But we waited till last > minute. And now you're telling us to wait more because there will be > a new release of the *interpreter*? FWIW, I was just making a suggestion, not directing an inviolable course of action. So calm down, calm down. If anything, perhaps we should at least put out an eselect news release that reads like an "under construction" notice to let users (and other devs) know that there's going to be some rough spots ahead while Py2 support is excised from the tree. If there's a tracker bug, then directing them to that as well so there's a way for people to follow the process of the removal and even help chase down loose ends. Again, that's just a suggestion, so please put the pitchforks down if ya'll don't like it. -- Joshua Kinard Gentoo/MIPS kumba@gentoo.org rsa6144/5C63F4E3F5C6C943 2015-04-27 177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic