Opened 17 years ago
Last modified 12 years ago
#6182 closed
python-markdown2 support in markup — at Version 2
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | contrib.markup | Version: | dev |
| Severity: | Normal | Keywords: | markdown markup |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
This is a patch to allow the usage of the python-markdown2 library in place of the original markdown library. They claim better performance but I just believe it should be an option. (so if somebody really wants markdown2, they make sure markdown isn't on the Python path)
Change History (3)
by , 17 years ago
| Attachment: | markdown2.patch added |
|---|
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 17 years ago
| Description: | modified (diff) |
|---|---|
| Patch needs improvement: | set |
| Triage Stage: | Design decision needed → Accepted |
For backwards compatibility purposes, it should probably behave exactly as it does now by default. That is, uses the markdown module if it is installed. There's no guarantee that markdown2 and markdown will produce exactly the same output in all cases (in fact, they don't).
Given how trivial it is to write a filter like this, it's not completely clear we need to include this, but it's not too harmful, providing it's the second option chosen.
patch to allow use of python-markdown2 in place of python-markdown