pagure

#3668 Update pfmarkdown
Closed: Fixed Opened by akanksham.

Closed: Fixed
Reopen Issue

Python-Markdown v3 was released today, and it introduces some breaking changes.

We can probably pin the markdown package to 2.6.11 for now, but I think it needs an update.

I'm up for doing this, if we choose to go with v3!

I'm up for doing this, if we choose to go with v3!

Seeing the production environment we and others deploy pagure on, we won't be
able to drop 2. So we would need a way to support both 2 and 3 :)

Okay. Off the top of my head, I think I can do it by applying conditions on markdown.__version__ in pfmarkdown and declaring the classes differently in each branch.
Is there a better way?

Was this issue solved, if not i am interested in solving this

This needs to be solved, since Markdown v3 went into openSUSE Factory, and will probably hit Rawhide soonish.

Metadata Update from @pingou:
- Issue set to the milestone: 5.3

Metadata Update from @pingou:
- Issue tagged with: RFE

Metadata Update from @pingou:
- Issue assigned to pingou

Metadata Update from @pingou:
- Issue set to the milestone: 5.2 (was: 5.3)

Commit 8ed43b1f fixes this issue
Metadata

RFE

None
None
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.