trentm / trentm/python-markdown2
Bad performance in _unescape_special_chars
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 459
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Description
Describe the bug
https://github.com/trentm/python-markdown2/blob/adf4e8199ec08ee2ade22eb80703cfb44decbbce/lib/markdown2.py#L2225
To Reproduce
Pretty hard as its a big markdown file
Expected behavior
A clear and concise description of what you expected to happen.
Debug info
Version of library being used:
Any extras being used:
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
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 at lib/markdown2.py around line 2225 and profile _unescape_special_chars with a large Markdown file, as the issue says reproduction is difficult. Identify the slow path and confirm that the change improves processing time without altering unescaping behavior; the issue provides no specific test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100