-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xml Content Handlers #240
Xml Content Handlers #240
Conversation
Codecov Report
@@ Coverage Diff @@
## master #240 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 58 62 +4
Lines 4473 4626 +153
Branches 767 780 +13
==========================================
+ Hits 4473 4626 +153
Continue to review full report at Codecov.
|
f2316e7
to
8ef2034
Compare
Interesting stuff I thought for sure the lxml sax approach without the element tree builder would be faster |
Next python built-in xml handlers 👍 |
92ddfa1
to
a812122
Compare
It looks good so far, the w3c suite has a few tests failing, that also fail with lxml without the recover mode because of some illegal characters. |
c821ca8
to
5436b18
Compare
Note: Introduced XmlHandler interface to bolt parsers and content handlers like sax.
The goal is to stop depending on lxml for parsing and add the ability to bolt other xml content handlers for whatever reason eg performance, custom processing, compatibility, issues etc etc
From travis