-
Notifications
You must be signed in to change notification settings - Fork 897
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: Python-Markdown/markdown
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3.10.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: Python-Markdown/markdown
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.10.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 21 files changed
- 6 contributors
Commits on Dec 3, 2025
-
Ensure nested elements inside inline comments are properly unescaped.
When inline Markdown elements are nested, each nested level contains its own placeholder. Therefore, when unescaping, the regex substitution needs to be run against each nested level. As this is nested inside the match, it ensures no more than one non-matching regex will be run in each instance. Closes #1571.
Configuration menu - View commit details
-
Copy full SHA for 2b49115 - Browse repository at this point
Copy the full SHA 2b49115View commit details
Commits on Dec 10, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 961856c - Browse repository at this point
Copy the full SHA 961856cView commit details
Commits on Dec 11, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 89112c2 - Browse repository at this point
Copy the full SHA 89112c2View commit details
Commits on Dec 29, 2025
-
Fix infinite loop when text contains multiple unclosed comments
The `updatepos()` override was resetting the parser position to `0`, causing infinite loops when multiple bogus/unclosed comments appeared in the input (e.g., `</` or `<!--` followed by non-standard characters). Now tracks the position of the triggering `<` and advances past it instead of rewinding to the start of the buffer. Fixes #1578. * update changelog
Configuration menu - View commit details
-
Copy full SHA for fb6b27a - Browse repository at this point
Copy the full SHA fb6b27aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 07dfa4e - Browse repository at this point
Copy the full SHA 07dfa4eView commit details
Commits on Dec 30, 2025
-
Revert "Allow reference links with backticks"
This reverts commit 07dfa4e.
Configuration menu - View commit details
-
Copy full SHA for 9933a0a - Browse repository at this point
Copy the full SHA 9933a0aView commit details
Commits on Jan 21, 2026
-
- Have `parse_comment` handle bad `<!--` cases. - `handle_comment` only needs to handle the `</` case for comments. Provide a more reliable way to calculate the index to check for this case. - Ensure `override_comment_update` is reset, just in case. Resolves #1586 * Fix spelling * Add changelog entry
Configuration menu - View commit details
-
Copy full SHA for f925349 - Browse repository at this point
Copy the full SHA f925349View commit details -
Configuration menu - View commit details
-
Copy full SHA for e5fa5b8 - Browse repository at this point
Copy the full SHA e5fa5b8View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 3.10.0...3.10.1