Skip to content

[Work Item #11111] Resolved ptest failures in python-markdown package#17089

Draft
durgajagadeesh wants to merge 1 commit intomicrosoft:3.0-devfrom
Kanishk-Bansal:topic_python-markdown-3.0
Draft

[Work Item #11111] Resolved ptest failures in python-markdown package#17089
durgajagadeesh wants to merge 1 commit intomicrosoft:3.0-devfrom
Kanishk-Bansal:topic_python-markdown-3.0

Conversation

@durgajagadeesh
Copy link
Copy Markdown
Contributor

@durgajagadeesh durgajagadeesh commented May 8, 2026

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
  • ./SPECS/python-markdown.spec
  • ./SPECS/0001-fix-htmlparser-incomplete-tags-and-comments.patch
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx
  • Patch has been applied cleanly.
image

@durgajagadeesh durgajagadeesh requested a review from a team as a code owner May 8, 2026 11:14
@durgajagadeesh durgajagadeesh marked this pull request as draft May 8, 2026 11:14
@microsoft-github-policy-service microsoft-github-policy-service Bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels May 8, 2026
@durgajagadeesh durgajagadeesh force-pushed the topic_python-markdown-3.0 branch from a31d4b4 to 8b2faaa Compare May 8, 2026 11:21
@durgajagadeesh durgajagadeesh force-pushed the topic_python-markdown-3.0 branch from 8b2faaa to 265443d Compare May 8, 2026 11:50
@durgajagadeesh
Copy link
Copy Markdown
Contributor Author

Backport upstream fix for Python-Markdown issue #1537 / PR #1539.
Adjust HTML parser handling for incomplete start tags and unclosed comments
to preserve historical Markdown behavior with newer CPython HTML parser changes.

@Kanishk-Bansal Kanishk-Bansal added the ptest package testing (%check section in spec) label May 8, 2026
Copy link
Copy Markdown
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix in 3.8.2
can we upgrade instead of this patch?

Python-Markdown/markdown@3.5.2...3.8.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging ptest package testing (%check section in spec)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants