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

Fred Baker <> Tue, 08 October 2019 21:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 91E4E120020; Tue, 8 Oct 2019 14:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id y9ySMo4GtUMM; Tue, 8 Oct 2019 14:47:12 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A4B3D120033; Tue, 8 Oct 2019 14:47:12 -0700 (PDT)
Received: by with SMTP id a2so167964pfo.10; Tue, 08 Oct 2019 14:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=1cLZ2UjtlMRh+eex+VxBVoOprTU34qj4OO1rUsD/wuI=; b=JJt7WrM0Ji+QHm9w0LgBjOZJ+iE2mHGWNxzjsi6M/ZMiJUwpRqG2CKcwDPx/R68kfh z21ccpqleo5nO9juKDFtyEt7mjQHChvoEWPp/tzpbfH7Ze5l5l2RpBSfDdK421sLSWvi 6wqjzFXbY1GVNmil90tt9qOX/t9DMPzPkfMi6DHiJuSlGUQtIoiD+Kux/XTwCtsQ2MC3 w8lpQ7/Wge03YXDeDSZG/Y1VSwuKFu9eTLlgfTVclkzUy5Z2AfWxbUgOFbKw6cdt3C0U KNQixt5fSWeYy38Rqy1yvDm0VlipvZbjm6J0oJ2dxAztDReeqGoxivC3uoTN99pFF/yC nTWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=1cLZ2UjtlMRh+eex+VxBVoOprTU34qj4OO1rUsD/wuI=; b=sQxCmuWyfAyuXrYchhsDSPJSSPuPkJPuQbkbuC8TXjVl/naz0IXLZfZl1xmE41rJiN jElvj07RRx8/YIn7Z9QNopXWvG81DGD4ByAaHlkQOL6vArGcdR0fzXdMpFeCWLaeUGSV +qdVKNbNWsCbbKcs8NtW81Jq77cCJF1enXdK8lHpJB+fGSNejSjEdGYoCsiuw0oE5vnR sc0k/d5nutP9TZKJgdAodNyXGNqwGDxO0vQbt9cEAfD9lXbzr2/bKAX7IRuQNGQVKMqG TVtAOncULXSETAnXhz9Y0XLeTwEBb4lKv4V1/f+IevOiTFMcQTD4elyPSKsmj9yH8RLt 1awg==
X-Gm-Message-State: APjAAAV9Zg1AbZJq5vo/kde0fu+qwklecX3dTAXJ/ISxwRtP2aoe0nWZ 947KIW9cIlDP5bkLQuEVgGcN/DJT
X-Google-Smtp-Source: APXvYqxvv1mjXacyxM5Og1tqsfRtJFg8sYBpepa0+c/fVuHydKsHorjXKLaP0BmJDzVX44uyQdb3ZA==
X-Received: by 2002:a62:d0:: with SMTP id 199mr107321pfa.108.1570571231952; Tue, 08 Oct 2019 14:47:11 -0700 (PDT)
Received: from ?IPv6:2601:648:8400:5ab0:98c9:b154:b31:7528? ([2601:648:8400:5ab0:98c9:b154:b31:7528]) by with ESMTPSA id 199sm84365pfv.152.2019. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Oct 2019 14:47:11 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Fred Baker <>
In-Reply-To: <>
Date: Tue, 8 Oct 2019 14:47:08 -0700
Cc: IETF <>,,,
Message-Id: <>
References: <>
To: Tools Team Discussion <>
X-Mailer: iPhone Mail (17B5059g)
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Oct 2019 21:47:15 -0000

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?

Sent using a machine that autocorrects in interesting ways...

> On Oct 8, 2019, at 2:31 PM, 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 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