Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon

Henrik Levkowetz <henrik@levkowetz.com> Wed, 09 October 2019 14:22 UTC

Return-Path: <henrik@levkowetz.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482B512084C; Wed, 9 Oct 2019 07:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLP3GvYvs2Oc; Wed, 9 Oct 2019 07:22:52 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C64120220; Wed, 9 Oct 2019 07:22:52 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:59788 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iICrZ-0001Zj-1E; Wed, 09 Oct 2019 07:22:50 -0700
To: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>, Job Snijders <job@instituut.net>
References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <858628DA-84DA-4982-89D7-D652E04ACA10@gmail.com> <da8ffcbf-33dd-6fe9-e251-0e3de47c611f@levkowetz.com> <CACWOCC-uuYGz54dExA5CwftowbpcBq4kQHJwCBWHNC1za_q70w@mail.gmail.com> <fc581783-1629-0a18-7c9c-0e5daeb425b8@it.aoyama.ac.jp>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, IETF <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>, Fred Baker <fredbaker.ietf@gmail.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <85192317-24ae-7f69-f523-ffc3f2400466@levkowetz.com>
Date: Wed, 9 Oct 2019 16:22:40 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <fc581783-1629-0a18-7c9c-0e5daeb425b8@it.aoyama.ac.jp>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FqlQI9njEgxgCXv6R4VETnWhnWIB7Xkgw"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: rfc-markdown@ietf.org, xml2rfc@ietf.org, fredbaker.ietf@gmail.com, tools-discuss@ietf.org, ietf@ietf.org, xml2rfc-dev@ietf.org, job@instituut.net, duerst@it.aoyama.ac.jp
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/0uSKDrs0NVVa4BPD1itwMS7zuXI>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2019 14:23:00 -0000

Hi Martin,

On 2019-10-09 08:52, Martin J. Dürst wrote:
> On 2019/10/09 09:00, Job Snijders wrote:
> 
>> Between the name of the tool (note the 2 in "xlm2rfc"), the industry's
>> transition from python 2 to python 3, and IETF's transition from the
>> v2 to the v3 RFC XML format, it is no surprise to me end users easily
>> become confused. A simple strong message that python2 can't be used
>> might be helpful, even if it appears somewhat unforgiving.
> 
> What about changing xml2rfc's name to xml3rfc? That way, xml3rfc, python 
> 3, v3 of RFC XML, and pip3 would all align :-).

True, but it would also break things for every person and script going to
the python package index to fetch the tool (https://pypi.org/project/xml2rfc/)
... ,:-)


Best regards,

	Henrik