turicas/rows

Optionally don't use lxml

Open

#152 opened on May 2, 2016

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (136 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (886 stars)
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

Research direction
Evaluate the feasibility of using Python's standard xml module as a fallback for lxml in all plugins. Compare performance and compatibility, and ensure no regressions in supported formats.
Tech stack
python
Domain
backendtooling
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonXML parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60