From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4633A1381F3 for ; Tue, 21 May 2013 14:47:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 800E9E0823; Tue, 21 May 2013 14:47:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 03069E0823 for ; Tue, 21 May 2013 14:47:04 +0000 (UTC) Received: from [192.168.1.210] (S010600222de111ff.vc.shawcable.net [96.49.5.156]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dolsen) by smtp.gentoo.org (Postfix) with ESMTPSA id 193E033E3A5 for ; Tue, 21 May 2013 14:47:04 +0000 (UTC) Message-ID: <1369147587.4863.5.camel@big_daddy.dol-sen.ca> Subject: Re: [gentoo-catalyst] Python 3 support From: Brian Dolbec To: gentoo-catalyst@lists.gentoo.org Date: Tue, 21 May 2013 07:46:27 -0700 In-Reply-To: <20130521112024.GN23990@odin.tremily.us> References: <519A9044.2050104@case.edu> <1369089959.30989.22.camel@big_daddy.dol-sen.ca> <20130521112024.GN23990@odin.tremily.us> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 33a43e5e-abb4-40bf-9c53-802c1e059fcd X-Archives-Hash: 9fa0be9e6a3e8afbe2a1036466fac7f1 On Tue, 2013-05-21 at 07:20 -0400, W. Trevor King wrote: > On Tue, May 21, 2013 at 12:33:28PM +0200, Dmitry Selyutin wrote: > > Even more, I'd like to avoid some generators and provide this > > support manually: I've always hated generators, especially code > > generators (and GUI ones). > > Generators? Are you referring to 2to3? I think anyone converting a > Python project from Python 2 to Python 3 would be cray not to use it. > They'd also be crazy if they just assumed that it generated optimal > code ;). It's best to run it, and then go double check to make sure > all the changes are meaningful. Keep stuff like [1]: > > - raise CatalystError, "Could not open file " + filename > + raise CatalystError("Could not open file " + filename) > > but drop stuff like: > > - for x in self.values.keys(): > + for x in list(self.values.keys()): > > Cheers, > Trevor > > [1]: Although see 305cde6 (Massive pyflakes import cleanup and broken > CatalystError calls, 2013-01-19) in dolsen's branch. There will > also be lots of `print ...` → `print(...)` changes, which are > needed unless we replaced them with calls to a logging logger > [2]. > [2]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2085/focus=2103 > I too was thinking of converting to using loggers. I want it to be something that is easy to re-direct. In that way it would be easier for alternate front-ends to be created. One such possibility could be a web front end or other server driven monitoring application.