IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Thu, 29 August 2019 19:59 UTC

Return-Path: <rjsparks@nostrum.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 10D11120BFF; Thu, 29 Aug 2019 12:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level:
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 etw78iX6K_vQ; Thu, 29 Aug 2019 12:59:08 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B218F120B48; Thu, 29 Aug 2019 12:59:08 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x7TJx3LT001983 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 29 Aug 2019 14:59:05 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1567108747; bh=+RTAW3IyikM7yhowY0fDC/74cseDWUpFIIcqrxFCtro=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=Y0ln6s/ru2J1uRuTEY7mtggPa8TIG13WpbFD0s065fjE3I7wODq6EY3uhcLyBkxKV RCyqFpB8hE++5C7SCitfGvWMAoW9/rFPljUM0G5h/62V4uRY37QNpKPIUSloZcMnOa csojSnTvpAyvDGmkmqfc2S7ypACujabhI/fXgfzM=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Robert Moskowitz <rgm@htt-consult.com>, Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1i2EMD-0002SA-UW@durif.tools.ietf.org> <d82ab9f2-5913-ad0e-dc05-2be319480a3c@htt-consult.com> <49ac6de5-b3ed-fee5-10d6-49c0b0540df6@nostrum.com> <1fc420c6-e836-4e6e-f073-2c50942226cc@htt-consult.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <301e0246-759c-b735-0427-8a40156164af@nostrum.com>
Date: Thu, 29 Aug 2019 14:59:03 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <1fc420c6-e836-4e6e-f073-2c50942226cc@htt-consult.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/uk0DnzMX1PCt0oxd7QUzWLiIyi8>
Subject: Re: [Rfc-markdown] [xml2rfc] New xml2rfc release: v2.25.0
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: Thu, 29 Aug 2019 19:59:10 -0000

On 8/29/19 2:57 PM, Robert Moskowitz wrote:
>
>
> On 8/29/19 3:35 PM, Robert Sparks wrote:
>> Hi Bob -
>>
>> The message is coming out of pip, and I suspect your default python 
>> is currently 2.7.
>>
>> If you run pip --version, it should tell you which version of python 
>> it's running on (and consequently which version it is installing 
>> packages for).
>
> Looks like I have a pip, pip2, and pip3 installed.  So a question for 
> the Fedora list.
>
>
>> There is only one xml2rfc - it can process both v2 and v3 documents. 
>> It also runs under either python 2 or python 3.
>
> So no surprises?   The big v3 reveal being discussed on the IETF list 
> will have no effect on drafts in development?
xml2rfc won't try to process your draft as v3 until you change the 
source to say it is v3 source, or you use the --v3 argument.
>
>
> thanks
>
>>
>> RjS
>>
>>
>> On 8/29/19 2:22 PM, 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.
>>>
>>> What is causing this message?  An old version of pip or xml2rfc?
>>>
>>> Is there a way to install xml2rfc v3 to start checking it out 
>>> without loosing v2?
>>>
>>> thanks
>>>
>>> _______________________________________________
>>> Rfc-markdown mailing list
>>> Rfc-markdown@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rfc-markdown
>>
>

v2.23.0 | Report a Bug | By Email