within from oneOrMore to zeroOrMore, in order to make it possible to honour the tocInclude setting, and reordered some true/false entries for consistency, and changed the line breaking of some lines in the RNG compact representation to fit on 72-character lines. * Added .rng and .rnc files with the RFC7991 schema, in order to be able to automatically determine which elements and attributes are new in the schema since 7991. * Added a new writer, 'doc', and template and text snippet files for autogenerated documentation. * Updated the requirements file with some new module requirements. * Refactured the code a bit to make it more straightforward to generate text without writing it out to file. * Moved the list of deprecated attributes to writers/base.py, and did some slight refactoring for consistent naming of some class variables and avoidance of duplicate parsing of the schema file. * Did some minor code cleanup and dead code removal, and corrected the header generation for non-IETF documents (using ). * Fixed an issue where XML parser errors could be reported for '' instead of the actual input file name. * Added new options --docfile/--doc and --manpage/--man, used to trigger generation and display of the built-in documentation. Reorganised the option grouping. Updated some option help strings. Made it possible to propagate all command-line option information to the documentation template. * Corrected the default templates path. This is related to change [3723]. * Reverted a change from [3722] in the v2v3 converter. * Added a custom Jinja2 filter 'capfirst()', for use in the documentation template. * Tweaked the documentation template: Some changed wording, support for sub-items not wrapped in , corrected capitalisation using the 'capfirst' filter. * Updated hastext() and iscomment() to do the right thing if given content with embedded xml processing instructions. * Tweaked the handling of default values for --date, so as to give better documentation of the option, and also tweaked the help text for --table-borders. * Added a class utility method to get any current PI related to a given setting, and fixed another case of template path default value, related to [3722]. * Added PI support for text table borders setting, and improved the text table output for transitions between and rows> for 'light' and 'minimal' borders. * Added makefile support for testing of the --manpage and --docfile switches. Added silencing of one unavoidable warning in the test of --unprep. -- Henrik Levkowetz 17 Jul 2020 14:07:39 -0700 The preferred way to install xml2rfc is by doing 'pip install xml2rfc', and 'pip install --upgrade xml2rfc' to upgrade. If there are system- installed python modules which pip will not upgrade, you may have to use 'pip install --upgrade --no-deps xml2rfc' and install dependencies manually. The new version is also available through SVN checkout, with 'svn checkout http://svn.tools.ietf.org/svn/tools/xml2rfc/tags/cli/2.47.0' Regards, Henrik (via the mkrelease script) From nobody Mon Jul 20 08:18:22 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDB93A0C3C; Mon, 20 Jul 2020 08:18:09 -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 2BAE4-HaLS8R; Mon, 20 Jul 2020 08:18:07 -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 A03CD3A0C37; Mon, 20 Jul 2020 08:18:07 -0700 (PDT) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:53993 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1jxXYL-0000nr-GY; Mon, 20 Jul 2020 08:18:07 -0700 To: Tools Team Discussion , IETF References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org From: Henrik Levkowetz Message-ID: <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com> Date: Mon, 20 Jul 2020 17:17:57 +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: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qxg1tUKcgKT89KbPNcC0ibiM6kxnJeAdE" 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: Subject: Re: [xml2rfc-dev] End of support for xml2rfc on Python 2.x is coming soon X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2020 15:18:09 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qxg1tUKcgKT89KbPNcC0ibiM6kxnJeAdE Content-Type: multipart/mixed; boundary="JDSUCIUdHNDE0lSCX8dRkiAekR5oRA24W"; protected-headers="v1" From: Henrik Levkowetz To: Tools Team Discussion , IETF Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org Message-ID: <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com> Subject: Re: End of support for xml2rfc on Python 2.x is coming soon References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> In-Reply-To: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> --JDSUCIUdHNDE0lSCX8dRkiAekR5oRA24W Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 af= ter IETF 108. Best regards, Henrik On 2019-10-08 23:23, Russ Housley wrote: > Heads up! >=20 > 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. >=20 > 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: >=20 > (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. >=20 > (2) The default output formatters will change to v3. The v2 formatters= > will still be available by using a --legacy switch. >=20 > Expect the first xml2rfc 3.x series release before the end of the month= =2E >=20 > On behalf of the Tools Team, > Russ >=20 >=20 --JDSUCIUdHNDE0lSCX8dRkiAekR5oRA24W-- --qxg1tUKcgKT89KbPNcC0ibiM6kxnJeAdE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl8VtaYACgkQTptXS4+7 Fxog0g//WBc6wwjIjmCEnK2dnnF20jKGE10ltiKROTjLR0U+mnJa3c7suSNAzbmq /v+mIOowNVTb6ZOGBSNTDHmn+yM9fF1Ezfmug9smLe4AITM88Cz6d4YLPnNBV6z8 aglcElWYgN883ixe2UkqLHApk/XR1FS5U9GPEXcXGGYr98xHKgHkn12xM0Zyz4If WU6BEdD74yQ6/uh1+JKGgY2awVjF2IRnV4khqM9ij9qPpmKLS2hBuPHkfH+31tQa KqiL1pVtr4LItX5OLk59sckuioj/j9WmohrrTvIucDHU7AL2c8Eusf9XGPN+jOH5 +oxbcvLAPlU6wb9N+W85rA08Y3nB2n22kTqwyCQKS4W+RKDRWxsM6N8ZsysI6tVL JTdR7o7WV7shYH4rSPKMCQrZlvl4FcmdGBZmedbQ4/qqnxsy64MNKDweEoAU95mJ 7CLey24zP2mSk8Iw4XJTtJTJkVVrVtwCX28GaCSnZ7htzqjB95WqruBspOvBPxKL VisVLmOKPGLLDtE1m7Nr8qaHtqu222S4QHZiTG2m3v3Z1a4NF/NSMi4+WX6OAH6Z Vmavkq/xmmsL4cZl9A/DmsZJWniex4SM7AKexup2bHUapKdKJ90/GmYyhNlPWGBp Q7Wlnm6g+H3CqSlXEJ2/sWc8g/BzLsoZTyJ3LJeQBC1C57JUEd4= =vZqV -----END PGP SIGNATURE----- --qxg1tUKcgKT89KbPNcC0ibiM6kxnJeAdE-- From nobody Mon Jul 20 10:41:30 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@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 ) id 1jxZms-0002Et-S0; Mon, 20 Jul 2020 10:41:15 -0700 To: Tools Team Discussion , IETF 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 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: Subject: Re: [xml2rfc-dev] End of support for xml2rfc on Python 2.x is coming soon X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2020 17:41:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --rJUhVg0f5EQdIifxHDfklsCJIeC4XupMG Content-Type: multipart/mixed; boundary="6anOXQ8sElXNCks352w5EbKEJUoRFh1nA"; protected-headers="v1" From: Henrik Levkowetz To: Tools Team Discussion , IETF Cc: rfc-markdown@ietf.org, xml2rfc@ietf.org, xml2rfc-dev@ietf.org Message-ID: <4f4adbcb-5b19-19ce-2465-8f49569e139a@levkowetz.com> Subject: Re: End of support for xml2rfc on Python 2.x is coming soon References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com> In-Reply-To: <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com> --6anOXQ8sElXNCks352w5EbKEJUoRFh1nA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2020-07-20 17:17, Henrik Levkowetz wrote: > Hi, >=20 > 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 vocabular= y (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_ forma= t will change to use the v3 renderer. xml2rfc will continue to accept v2 i= nput, but by default it will send it through the v2-to-v3 converter, and proces= s the resulting v3 xml through the v3 formatters. If you want to use the v2 formatters directly from the v2 XML, you will n= eed to give the --legacy switch to xml2rfc. Best regards, Henrik > Best regards, >=20 > Henrik >=20 > On 2019-10-08 23:23, Russ Housley wrote: >> Heads up! >>=20 >> With the transition to xml2rfc vocabulary version 3, xml2rfc has gaine= d >> 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. >>=20 >> The latest xml2rfc release is 2.32.0. There will most likely be one o= r >> 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:= >>=20 >> (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. >>=20 >> (2) The default output formatters will change to v3. The v2 formatter= s >> will still be available by using a --legacy switch. >>=20 >> Expect the first xml2rfc 3.x series release before the end of the mont= h. >>=20 >> On behalf of the Tools Team, >> Russ >>=20 >>=20 >=20 --6anOXQ8sElXNCks352w5EbKEJUoRFh1nA-- --rJUhVg0f5EQdIifxHDfklsCJIeC4XupMG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl8V1zMACgkQTptXS4+7 Fxpi0hAAsznwUheHDsc5qDtPP2IAmSafUZrqggKxn+/goDc+O6NiRlHIajwp+RUv oLaa0eF5ELOAl6nqN/9Zmav3XzM7hpedkBT6taaSH7uWcQueH44OPp5zGmOvIpWs 2QDh54RvRX97WaVsOLuic6JwmIV+B19pRPF3lecZL26IvbLi37v6Nb1vo9ZVl4nJ OkDorWhzV6osvzCE2VSTGVb4OFdl9W2ToCZfTDCagUNQTirMm7kHvxfvMNTOAQkQ W72gmc7qY5/BC5Zix41xbRE/uub4Ruz7MZFID29e8zRIACLVYAT+ipVpinsnK3DN oPoXv8Cjjaev8Wnw4lS++L5KIjhOBsuT+i8ALwnE+0ENTQbCzu054AYinL/mUF56 7Z51pfwjdNfsdRBztCPY3sKC892GUMb2epONLByl2vN22gEgYzjY+a59S2D68dq9 pZWr8y3QxYaCljp8XBBnnl1oTrE927SCbCtsAU1o22aFUFNTnfI3EPMfZE05geX/ ngUbMDs5O+LEqUlSitkHTk3A1nFoBM9Sr3uQPvqBXuPy4Zt5RONHsAoOKTywXJzN hMdIySHBazCodOYIfH0M+zBppZXifrwyPv2a408hhfSBSufgJD1802YGfvHKwe/L GnYHNRnRygYjGKK8h4eUR2vc3IMTfaXMLSXiGnFmk6GNyGnwSzY= =jhHT -----END PGP SIGNATURE----- --rJUhVg0f5EQdIifxHDfklsCJIeC4XupMG-- From nobody Mon Jul 20 12:25:07 2020 Return-Path: X-Original-To: xml2rfc-dev@ietfa.amsl.com Delivered-To: xml2rfc-dev@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEB93A0E34; Mon, 20 Jul 2020 12:24:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aRRKPuOQvCl9; Mon, 20 Jul 2020 12:24:52 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62C6D3A0E41; Mon, 20 Jul 2020 12:24:50 -0700 (PDT) Received: from [172.16.42.100] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4B9WrX4kXDzyXk; Mon, 20 Jul 2020 21:24:44 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) From: Carsten Bormann In-Reply-To: <4f4adbcb-5b19-19ce-2465-8f49569e139a@levkowetz.com> Date: Mon, 20 Jul 2020 21:24:43 +0200 Cc: Tools Team Discussion , IETF , rfc-markdown@ietf.org, XML2RFC Interest Group , XML Developer List X-Mao-Original-Outgoing-Id: 616965883.96795-cdae1ba58884b308ca21f79ef4572961 Content-Transfer-Encoding: quoted-printable Message-Id: References: <082EE9F1-D4AA-487F-BB8C-08CDB59C5A2F@vigilsec.com> <82e10650-8f68-26b2-df22-dff93ce72ee0@levkowetz.com> <4f4adbcb-5b19-19ce-2465-8f49569e139a@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.3608.120.23.2.1) Archived-At: Subject: Re: [xml2rfc-dev] [xml2rfc] End of support for xml2rfc on Python 2.x is coming soon X-BeenThere: xml2rfc-dev@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2020 19:24:55 -0000 On 2020-07-20, at 19:41, Henrik Levkowetz wrote: >=20 > 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. >=20 > If you want to use the v2 formatters directly from the v2 XML, you = will need > to give the --legacy switch to xml2rfc. Makes a lot of sense to me. The v2-to-v3 converter seems to work very well, and continuing to = support all the XML2RFCv2 files lying around (and still being generated) = is the right approach as well. Thank you, Henrik! Gr=C3=BC=C3=9Fe, Carsten