SourceForgeMark

Sounds good! I'm curious what your thoughts on the patch posted by Andre. https://github.com/andrebrait/1g1r-romset-generator/commit/402ef60534ae4e25bd64eb066caf0f93dde84373 Could that be a compromise? The next major release could then require lxml? On Tue, Aug 17, 2021 at 5:19 PM Dave Kuhlman dkuhlman@users.sourceforge.net wrote: Mark, I've removed the try/except from around the import of lxml. I agree with you. That was a trap waiting to bite someone. I apologize that it was you. I worry that there...

Actually, I think my suggestion was poor! =) I think we can just remove the try import statement from the generated code i.e. changing try: from lxml import etree as etree_ except ModulenotfoundExp_ : from xml.etree import ElementTree as etree_ to just from lxml import etree as etree_ We won't know what python environment the user is running the generated python script from so by forcing the lxml import the user will know that lxml is required. Perhaps this requirement to run generated python scripts...

"AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'prefix' " because lxml not installed

minor update

added tell call to m8r.py

added python utility

added include guard

adding utility files in my user directory (mlai...