refactor: update markdown to 3.8 and adapt extension code for compatibility

[wgu-ram-chandra]

Purpose

This PR resolves a compatibility issue with the markdown dependency, which surfaced while addressing edx-platform issue #35271.

Background

The edx-platform currently pins markdown to <3.4.0. When attempting to lift that constraint and upgrade markdown to the latest version (3.8), tests in this repository failed due to breaking changes introduced in markdown>=3.4.0.

As outlined in the markdown 3.4 release notes, key breaking changes include:

• Removal of the md_globals parameter from Extension.extendMarkdown()
• Replacing the .add() method with .register() in processor registration
• Changing the argument order and priority system in processor registration
• Refactoring of markdown.util.etree to use the standard library's xml.etree.ElementTree

Below is a sample illustration of changes from the 3.4 release notes

Changes Made

• Upgraded markdown to version 3.8 in base.in and test.in

• Refactored custom Markdown extensions to:

  • Remove deprecated md_globals usage
  • Replace add() with register() for preprocessor and treeprocessor registration
  • Use integer-based priority values instead of deprecated string-based values (e.g., '>inline', '>html_block')

• Ensured compatibility with the updated Markdown processing API

• Verified all tests pass after the upgrade

Follow-Up

Once this PR is merged, it will unblock and help resolve:
edx-platform issue #35271

References

• https://github.com/Python-Markdown/markdown/blob/3.4/docs/change_log/release-3.4.md
• https://github.com/Python-Markdown/markdown/tree/master/markdown

[UsamaSadiq]

You need to run make upgrade using Python 3.12 env to keep the requirements consistent across all open edX repositories.
Other than that the changes look good to merge.

[openedx-webhooks]

Thanks for the pull request, @wgu-ram-chandra!

This repository is currently maintained by @2U-aperture.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[wgu-ram-chandra]

Hi @UsamaSadiq, earlier when I ran make upgrade, it also upgraded some other dependencies like tox and pluggy, which I wasn’t expecting. I had started cleaning that up but stepped away from my computer. I've now re-run make upgrade correctly and pushed the updated changes. Let me know if there's anything else you'd like me to adjust!

[UsamaSadiq]

Looks good to merge.

[wgu-ram-chandra]

Thanks @UsamaSadiq! Could you please merge this PR when you get a chance? I don’t have the necessary permissions to do so.

[UsamaSadiq]

Sure. You may also need to bump the package version if you need this package updated in edx-platform.
Update package CHANGE LOG and bump version in __init__.py file and I'll go ahead and merge it.

[wgu-ram-chandra]

Hi @UsamaSadiq, I’ve made the changes you requested, including bumping the version in setup.py and adding a changelog for the release. Please have a look and let me know if everything looks good or if any further updates are needed.

[UsamaSadiq]

package version https://pypi.org/project/openedx-django-wiki/3.1.1/ has been released with this change on PyPI

[wgu-ram-chandra]

Thank you @UsamaSadiq!