Re: [TOOLS-DEVELOPMENT] Preview release of Text Submission Converter, id2xml

[Henrik Levkowetz <[e-mail]>]

Hi Sandy,

Responding off list.


Best,

	Henrik

On 2017-05-15 22:38, Sandy Ginoza wrote:
> Hi all,
> 
> Please note that I’ve added Megan Ferguson to the thread, as she is the lead for testing v3-related tools for the RPC.  
> 
> We haven’t been able to successfully run id2xml yet.  Matt installed the updated version for us this morning to see if that helped, but we’re still getting the same errors and we’re unable to view output of "id2xml —help"
> 
> Are we missing something?  Some of the error messages are below.
> 
> Thanks!
> Sandy
> 
>> > id2xml draft-ietf-rtgwg-yang-key-chain-24test.txt
>> Traceback (most recent call last):
>>  File "/usr/bin/id2xml", line 9, in <module>
>>    load_entry_point('id2xml==0.9.1', 'console_scripts', 'id2xml')()
>>  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 558, in load_entry_point
>>    return get_distribution(dist).load_entry_point(group, name)
>>  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2682, in load_entry_point
>>    return ep.load()
>>  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2355, in load
>>    return self.resolve()
>>  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2361, in resolve
>>    module = __import__(self.module_name, fromlist=['__name__'], level=0)
>>  File "/usr/lib/python3.4/site-packages/id2xml/parser.py", line 43, in <module>
>>    from __init__ import __version__
>> ImportError: No module named ‘__init__'
> 
>> id2xml draft-ietf-sidr-rpki-oob-setup-09.txt > draft-ietf-sidr-rpki-oob-setup-test.xml
> Traceback (most recent call last):
>   File "/usr/bin/id2xml", line 9, in <module>
>     load_entry_point('id2xml==0.9.1', 'console_scripts', 'id2xml')()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 558, in load_entry_point
>     return get_distribution(dist).load_entry_point(group, name)
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2682, in load_entry_point
>     return ep.load()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2355, in load
>     return self.resolve()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2361, in resolve
>     module = __import__(self.module_name, fromlist=['__name__'], level=0)
>   File "/usr/lib/python3.4/site-packages/id2xml/parser.py", line 43, in <module>
>     from __init__ import __version__
> ImportError: No module named ‘__init__'
> 
> 
>> id2xml draft-ietf-sidr-rpki-oob-setup-09.txt | draft-ietf-sidr-rpki-oob-setup-test.xml
> If 'draft-ietf-sidr-rpki-oob-setup-test.xml' is not a typo you can use command-not-found to lookup the package that contains it, like this:
>     cnf draft-ietf-sidr-rpki-oob-setup-test.xml
> Traceback (most recent call last):
>   File "/usr/bin/id2xml", line 9, in <module>
>     load_entry_point('id2xml==0.9.2', 'console_scripts', 'id2xml')()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 558, in load_entry_point
>     return get_distribution(dist).load_entry_point(group, name)
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2682, in load_entry_point
>     return ep.load()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2355, in load
>     return self.resolve()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2361, in resolve
>     module = __import__(self.module_name, fromlist=['__name__'], level=0)
>   File "/usr/lib/python3.4/site-packages/id2xml/parser.py", line 44, in <module>
>     from __init__ import __version__
> ImportError: No module named ‘__init__'
> 
> 
>> id2xml --help
> Traceback (most recent call last):
>   File "/usr/bin/id2xml", line 9, in <module>
>     load_entry_point('id2xml==0.9.2', 'console_scripts', 'id2xml')()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 558, in load_entry_point
>     return get_distribution(dist).load_entry_point(group, name)
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2682, in load_entry_point
>     return ep.load()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2355, in load
>     return self.resolve()
>   File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2361, in resolve
>     module = __import__(self.module_name, fromlist=['__name__'], level=0)
>   File "/usr/lib/python3.4/site-packages/id2xml/parser.py", line 44, in <module>
>     from __init__ import __version__
> ImportError: No module named '__init__'
> 
> 
> 
> 
>> On May 15, 2017, at 1:15 PM, Robert Sparks <[e-mail]> wrote:
>> 
>> 
>> 
>> On 5/15/17 3:53 PM, Russ Housley wrote:
>>> Henrik:
>>> 
>>> After  $ pip install id2xml, what is the command line to produce a .xml form a .txt that contains an RFC or Internet-Draft?
>> id2xml draft-whatever.txt
>> 
>> id2xml --help shows a lot of options
>>> 
>>> Russ
>>> 
>>> 
>>> 
>>>> On May 15, 2017, at 6:59 AM, Henrik Levkowetz <[e-mail]> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I've just uploaded the third preview release (0.9.2) of 'id2xml', the
>>>> text-submission converter tool:
>>>> 
>>>>  https://pypi.python.org/pypi/id2xml
>>>> 
>>>> You should be able to install it with:
>>>> 
>>>>  $ pip install id2xml
>>>> 
>>>> All feedback is very welcome.
>>>> 
>>>> 
>>>> From the README file:
>>>> 
>>>> This tool, 'id2xml', is intended for use by the RFC-Editor staff, in order to
>>>> produce a first xml2rfc-compatible XML version from text-only Internet-Draft
>>>> submissions.
>>>> 
>>>> id2xml may also be useful for Internet-Draft authors who wish to start working
>>>> on a new version of an older draft or RFC, for which no xml2rfc-compatible XML
>>>> source is available.
>>>> 
>>>> The releases of the 0.9.x release series are preview releases, with a number
>>>> of known deficiencies.  They are released in order that potential users may
>>>> provide feedback on the most desired improvements ahead of a 1.0.0 release.
>>>> 
>>>> Version 0.9.0 can process the drafts specified in the development Statement of
>>>> Work to XML files acceptable to xml2rfc, and can also process a number of
>>>> other test files to acceptable XML.  However, adding new drafts to the test
>>>> set still reveals weaknesses in many cases, so trouble-free processing of any
>>>> arbitrary draft should not be expected from the 0.9.x series.
>>>> 
>>>> The XML produced follows RFC 7749 [1]_ in version 0.9.x and 1.x of the tool, and will follow RFC 7991 [2]_ in version 2.x, which will be released once
>>>> support is available to process XML sources which follows the RFC 7991
>>>> vocabulary.
>>>> 
>>>> 
>>>> .. [1] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", RFC 7749, DOI
>>>>   10.17487/RFC7749, February 2016, <http://www.rfc-editor.org/info/rfc7749>.
>>>> 
>>>> .. [2] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI
>>>>   10.17487/RFC7991, December 2016, http://www.rfc-editor.org/info/rfc7991>.
>>>> 
>>>> 
>>>> Best regards,
>>>> 
>>>> 	Henrik
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> TOOLS-DEVELOPMENT mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/tools-development
>>> _______________________________________________
>>> TOOLS-DEVELOPMENT mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/tools-development
>> 
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/tools-development
>> 
> 
>