Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0

Henrik Levkowetz <> Thu, 29 August 2019 20:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D939E1208DD; Thu, 29 Aug 2019 13:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vm4PtdEcf0bv; Thu, 29 Aug 2019 13:24:28 -0700 (PDT)
Received: from ( [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7A87A12001B; Thu, 29 Aug 2019 13:24:28 -0700 (PDT)
Received: from ([]:60560 helo=tannat.localdomain) by with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1i3Qy3-00007g-EI; Thu, 29 Aug 2019 13:24:28 -0700
To: Robert Moskowitz <>,,
References: <> <>
From: Henrik Levkowetz <>
Message-ID: <>
Date: Thu, 29 Aug 2019 22:24:19 +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: <>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UubANVQJxgQHShtJDdGRSO3mA8vawaO1X"
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0
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: Thu, 29 Aug 2019 20:24:30 -0000

Hi Bob,

On 2019-08-29 21:22, Robert Moskowitz wrote:
> On 8/26/19 8:44 AM, Henrik Levkowetz wrote:
>> Hi,
>> This is an automatic notification about a new xml2rfc release,
>> v2.25.0, generated when running the mkrelease script.
> Notes on my experience with the upgrade:
> I get the standard warning:
> DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 
> 2020. Please upgrade your Python as Python 2.7 won't be maintained after 
> that date. A future version of pip will drop support for Python 2.7.
> I have both Python2 and 3 installed on my Fedora 30 system.

This warning indicates either that the default python is still 2.7, or
that the pip command you are running is symlinked to pip-2.7.

> What is causing this message?  An old version of pip or xml2rfc?

Pip.  The pip that comes with Python 2.7 gives the warning above.

Irrespective of which pip and python you use (2.7, 3.5, 3.6, 3.7),
the installed version of xml2rfc now supports vocabulary v3.

> Is there a way to install xml2rfc v3 to start checking it out without 
> loosing v2?

xml2rfc v2 and v3 are supported by the same install.  In order to produce
v3 output, use 'xml2rfc --v3 ...'.  In order to convert your v2 xml files
to v3 xml, use 'xml2rfc --v2v3 ...'.

Note that when speaking about 'v3' xml2rfc, there is a certain need to
indicate which aspect of xml2rfc v3 support you are referring to:

There is both the matter of the v3 xml vocabulary, where many v2 constructs
are deprecated; and there are the v3 formatters, which are completely
rewritten to handle the v3 xml.

Now, having made that clear, I'm afraid that the following may cause some
blurring again, but it's been done in the interest of making forward progress
easier:  If you invoke one of the v3 formatters, by saying for instance
'xml2rfc --v3 --text ...', but your input file uses deprecated v2 elements,
those will be quietly converted internally, using the v2-to-v3 converter,
and then handed to the v3 formatter.  This of course adds a bit of magic
to the process, and you will have better control of your output if you work
with clean v3 input files.  Converting your v2 files to v3 with --v2v3 should
give you a good starting point for that.

I hope that helps.

Best regards,