Closed pcm1289 closed 2 months ago
@oddhack can you review this?
@oddhack can you review this?
Sorry, I overlooked this. It is true that ElementTree is API-compatible for the functionality we use here, but it actually isn't semantically compatible in some corner cases including one we might use in the scripts. I'll take a look and if the outputs are identical, we can just use ElementTree.
@oddhack can you review this?
Sorry, I overlooked this. It is true that ElementTree is API-compatible for the functionality we use here, but it actually isn't semantically compatible in some corner cases including one we might use in the scripts. I'll take a look and if the outputs are identical, we can just use ElementTree.
Verified we can replace lxml entirely for purposes of this repo. Suggest closing this and I'll merge #200 instead.
@pcm1289 could you look at #200 and see if that will work for you as an alternate? If so, please comment over there - I cannot assign you as a reviewer because GitHub - and close this.
Yep, that works. Thanks, closing
After installing the
lxml
dependency in MSYS on Windows using:..there was still an error:
It appears as if these may be well known because this website presented an alternative for those not depending explicitly on functions included in the
lxml
implementation ofetree
, found here: https://lxml.de/tutorial.htmlUpon making this change..
..the ability to use
make
out of the box was restored:This pull request addresses this. A visual inspection of
reg.py
on surface level looks to not use anylxml.etree
specific functions.