On 2019/10/09 09:00, Job Snijders wrote: > Between the name of the tool (note the 2 in "xlm2rfc"), the industry's > transition from python 2 to python 3, and IETF's transition from the > v2 to the v3 RFC XML format, it is no surprise to me end users easily > become confused. A simple strong message that python2 can't be used > might be helpful, even if it appears somewhat unforgiving. What about changing xml2rfc's name to xml3rfc? That way, xml3rfc, python 3, v3 of RFC XML, and pip3 would all align :-). Regards, Martin.
