aboutsummaryrefslogtreecommitdiff
path: root/svg-flatten/testdata/svg/vectorizer_simple.svg
diff options
context:
space:
mode:
authorjaseg <git@jaseg.de>2024-07-05 11:13:25 +0200
committerjaseg <git@jaseg.de>2024-07-05 12:37:42 +0200
commitbd2b3733ee87bd918c9ea7ca8f871951f7f86bca (patch)
treec348aa5d757abceafdd6ee1bd86f0ab5c4a705d5 /svg-flatten/testdata/svg/vectorizer_simple.svg
parent534c2e4ea3229c6ffef640ea8b55b0c18e02fd7b (diff)
downloadgerbolyze-bd2b3733ee87bd918c9ea7ca8f871951f7f86bca.tar.gz
gerbolyze-bd2b3733ee87bd918c9ea7ca8f871951f7f86bca.tar.bz2
gerbolyze-bd2b3733ee87bd918c9ea7ca8f871951f7f86bca.zip
Move from bs4 to etree
BeautifulSoup when using lxml in XML mode would mis-parse XML with very long attributes. Specifically, a <polygon> with about 18MB in its points attr would make lxml not return anything past that point in the file. bs4 uses lxml, which uses libxml2. libxml2 has a config option for parsing "huge" files that increases buffer sizes and avoids this error, and this option is exposed in lxml, but AFAICT you can't tell bs4 to set it, and bs4 just silently swallows the error from lxml. Fixes one half of #46
Diffstat (limited to 'svg-flatten/testdata/svg/vectorizer_simple.svg')
0 files changed, 0 insertions, 0 deletions