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

Henrik Levkowetz <henrik@levkowetz.com> Tue, 08 October 2019 22:23 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 B1E2A120046; Tue, 8 Oct 2019 15:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.095
X-Spam-Level:
X-Spam-Status: No, score=-1.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 1eP78JH_33id; Tue, 8 Oct 2019 15:23:20 -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 23709120020; Tue, 8 Oct 2019 15:23:20 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:52081 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 1iHxt0-0003V0-Iz; Tue, 08 Oct 2019 15:23:19 -0700
To: Fred Baker <fredbaker.ietf@gmail.com>, Tools Team Discussion <tools-discuss@ietf.org>
References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <858628DA-84DA-4982-89D7-D652E04ACA10@gmail.com>
Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org, IETF <ietf@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <da8ffcbf-33dd-6fe9-e251-0e3de47c611f@levkowetz.com>
Date: Wed, 9 Oct 2019 00:23:09 +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: <858628DA-84DA-4982-89D7-D652E04ACA10@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SU6IGfPOISu6mm8qWtIOXANrO8NA2OL1f"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: ietf@ietf.org, xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, tools-discuss@ietf.org, fredbaker.ietf@gmail.com
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/ynq6B5mNNyHTg7WymTZqzsKMfiM>
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: Tue, 08 Oct 2019 22:23:22 -0000

Hi Fred,

On 2019-10-08 23:47, Fred Baker wrote:
> That all fine, and as predictable as you say. What would very helpful
> would be a road map: if you’re using {windows X|Mac X|Linux
> X|whatever}, we think you should look at tools {D,E,F}.
> 
> Speaking personally, I am on a Mac and using XMLmind with Fenner’s
> tools. They mostly worked (note the past tense) except when they
> didn’t. Telling me “well, ABCDEF supports <IETF tools du jour if you
> can read Sanskrit>“ doesn’t quite work.
> 
> I used to write in NROFF. I’ll do what it takes. But really?

I'm sorry if the text wasn't clear enough.  The roadmap is this:  Please
install Python 3.5 or higher on your system, and install coming versions
of xml2rfc using the 'pip3' command which is part of that Python install.

When we got to the xml2rfc 3.0.0 release, I had planned to update the
release note with the information about using pip3, but I'm perfectly
happy saying it now, too.

Of course, if your default python is Python 3.5 or higher already, then
using plain 'pip' to install will continue to work.


Best regards,

	Henrik

> 
> Sent using a machine that autocorrects in interesting ways...
> 
>> On Oct 8, 2019, at 2:31 PM, Russ Housley <housley@vigilsec.com>; 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
>> 
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
> 
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>