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

Henrik Levkowetz <henrik@levkowetz.com> Mon, 20 July 2020 17:41 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 66C4E3A0D8E; Mon, 20 Jul 2020 10:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 5CLQ8vZA1z6V; Mon, 20 Jul 2020 10:41:15 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAD663A0D79; Mon, 20 Jul 2020 10:41:15 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:55815 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 1jxZms-0002Et-S0; Mon, 20 Jul 2020 10:41:15 -0700
To: Tools Team Discussion <tools-discuss@ietf.org>, IETF <ietf@ietf.org>
References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com>
Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <4f4adbcb-5b19-19ce-2465-8f49569e139a@levkowetz.com>
Date: Mon, 20 Jul 2020 19:41:07 +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: <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rJUhVg0f5EQdIifxHDfklsCJIeC4XupMG"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, ietf@ietf.org, tools-discuss@ietf.org
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/zNzEQhbCZK3r_DZkSIlhD_oFK-Q>
Subject: Re: [Rfc-markdown] 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: Mon, 20 Jul 2020 17:41:18 -0000

On 2020-07-20 17:17, Henrik Levkowetz wrote:
> Hi,
> 
> It's taken a lot longer than we thought, but I expect the next release of
> xml2rfc to be 3.0.0.  I currently plan to do the 3.0.0 release shortly after
> IETF 108.

I've been asked to clarify whether the conversion to 3.0.0 will mean the
end of support for the v2 (RFC 7749) vocabulary or whether that vocabulary
(DTD/Schema) will continue to be supported.

Short: The v2 vocabulary will continue to be supported.

The longer answer is that (as indicated below) the default _output_ format
will change to use the v3 renderer.  xml2rfc will continue to accept v2 input,
but by default it will send it through the v2-to-v3 converter, and process
the resulting v3 xml through the v3 formatters.

If you want to use the v2 formatters directly from the v2 XML, you will need
to give the --legacy switch to xml2rfc.


Best regards,

	Henrik

> Best regards,
> 
> 	Henrik
> 
> On 2019-10-08 23:23, Russ Housley wrote:
>> Heads up!
>> 
>> With the transition to xml2rfc vocabulary version 3, xml2rfc has gained
>> the ability to generate PDF output when the necessary system libraries
>> are installed.  However, xml2rfc runs on Python 2.7, but the library
>> needed for PDF generation ended support for Python 2.7 about 10
>> releases ago.  This means that the need to end support for xml2rfc on
>> Python 2.7 is becoming urgent.  Another factor is that bugfix support
>> for Python 2.7.x itself officially stops on 1 January 2020, so we need
>> to transition away from Python 2.7 soon in any case.
>> 
>> The latest xml2rfc release is 2.32.0.  There will most likely be one or
>> two additional xml2rfc releases in the 2.x series, but after that, the
>> plan is to transition to a 3.x release series, with two major changes:
>> 
>> (1) xml2rfc will no longer run under Python 2.7; it will require
>>     Python 3.5 or higher.  If you cannot install and run Python 3 on
>>     your system, the web service at xml2rfc.ietf.org can be used.
>> 
>> (2) The default output formatters will change to v3.  The v2 formatters
>>     will still be available by using a --legacy switch.
>> 
>> Expect the first xml2rfc 3.x series release before the end of the month.
>> 
>> On behalf of the Tools Team,
>>   Russ
>> 
>> 
>