Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1084815ybe; Thu, 5 Sep 2019 10:04:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqyf0tf2XlThnLF4ed0EEAZiwRhvBikaSAy1Gm77QRkpeNqYYNdWevWmpySikmr96ZGxp8vB X-Received: by 2002:a65:51c5:: with SMTP id i5mr4103643pgq.312.1567703051187; Thu, 05 Sep 2019 10:04:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567703051; cv=none; d=google.com; s=arc-20160816; b=AJiZekNLJ341Di2EKdjzzElFcZMVJXITJ4XxqlOwCDwUZuL0naXN9dXlbyNb+HPT3e Y0IWcb4plDvuqfJ29BsTre2zzJMJh+M0IlKBbej/yw5kpIrHEexBL4IF+/G7SqlZSmbH Mn9EHQJHBwcJSThO7m9fjuSnH/JpjtKh4G3ej2naanhMOZELzPFr7bneix+guu5r080q Bdu/98nUzCTn+3CpoHHVIvI5hV1vF6IWljfBLXa9ZPfwOOoVca//btV56QI8o3A++Rwh FVy2gPqwFn4C9zDjPOGQh6qBvnh5+WsWCb1SOOdYuEebJJeT9YSujxGy3p7nijkORYXk Xbsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=4TNht9HPDzbLCEAfyBXbJYVRAGdPNcm9rwrXvCYm6R0=; b=Po0kST1EMQJrUeN6BImemkh4FO2QtU6GrZE+Q0Halbl7syLyjq4caIBr+LmN2lgZqs z5JnY8E6W608A8MVFZ6lVhtAuOfSaVG2aa+XrSEMaDuLUixSCqo1cX6rQ3kPddd2kKBo Ir0judL5AYuRnMBMjYSxQnmiB+xCH04owIb6Sj/vJ3pqQMBJHY8VEOmAZpEAqif7Q+Di AsRY7Zy6mg+GmIXlbadVhuxNPHGsabB9AMkAB8MwZ3DIZD64rsPrjnlUKXGRoW/M9B+i H3Nv/r+cE/gkst96NRKvn40r9aLKQtBrPLZtTnuJS/CgfUGoWvtYHbPXxtl3SLrT7E0A haag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q5si2466169plr.309.2019.09.05.10.03.50; Thu, 05 Sep 2019 10:04:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387843AbfIEM5E (ORCPT + 99 others); Thu, 5 Sep 2019 08:57:04 -0400 Received: from ms.lwn.net ([45.79.88.28]:56832 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731008AbfIEM5D (ORCPT ); Thu, 5 Sep 2019 08:57:03 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id EB1176EC; Thu, 5 Sep 2019 12:57:02 +0000 (UTC) Date: Thu, 5 Sep 2019 06:57:01 -0600 From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Linux Media Mailing List , Mauro Carvalho Chehab , Greg Kroah-Hartman , Joe Perches , linux-kernel@vger.kernel.org, Jessica Yu , Federico Vaga , Thomas Gleixner , linux-doc@vger.kernel.org Subject: Re: [PATCH] docs: license-rules.txt: cover SPDX headers on Python scripts Message-ID: <20190905065701.4744e66a@lwn.net> In-Reply-To: <88e638eb959095ab6657d295f9f8c27169569bf2.1567675272.git.mchehab+samsung@kernel.org> References: <20190905055614.7958918b@coco.lan> <88e638eb959095ab6657d295f9f8c27169569bf2.1567675272.git.mchehab+samsung@kernel.org> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Sep 2019 06:23:13 -0300 Mauro Carvalho Chehab wrote: > Python's PEP-263 [1] dictates that an script that needs to default to > UTF-8 encoding has to follow this rule: > > 'Python will default to ASCII as standard encoding if no other > encoding hints are given. > > To define a source code encoding, a magic comment must be placed > into the source files either as first or second line in the file' So this is only Python 2, right? Python 3 is UTF8 by default. Given that Python 2 is EOL in January, is this something we should be concerned about? Or should we instead be making sure that all the Python we have in-tree works properly with Python 3 and be done with it? Thanks, jon