Optionally don't use lxml
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Python
- Stars
- 886
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
If we can use Python standard library's xml module instead of lxml, then we should move all plugins which use it to xml (but use lxml if available, since it's probably faster).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the plugins that import or depend on lxml, then compare their use with the Python standard library's xml module. Confirm how optional lxml availability is detected and run the relevant plugin tests; done means the plugins work with xml alone while using lxml when it is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, xml
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100