-
-
Notifications
You must be signed in to change notification settings - Fork 115
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: mkdocstrings/mkdocstrings
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.29.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: mkdocstrings/mkdocstrings
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.29.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 20 files changed
- 2 contributors
Commits on Mar 14, 2025
-
Configuration menu - View commit details
-
Copy full SHA for ba98661 - Browse repository at this point
Copy the full SHA ba98661View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9464579 - Browse repository at this point
Copy the full SHA 9464579View commit details -
Configuration menu - View commit details
-
Copy full SHA for 983b3cd - Browse repository at this point
Copy the full SHA 983b3cdView commit details
Commits on Mar 28, 2025
-
Configuration menu - View commit details
-
Copy full SHA for ccf65c1 - Browse repository at this point
Copy the full SHA ccf65c1View commit details
Commits on Mar 31, 2025
-
style: Format and configure for Ruff >= 0.10.0
Ruff 0.10.0 introduces the S704 lint, which triggers when a non- literal string is passed to `markupsafe.Markup()`. This triggered 5 times in the codebase. Only one of these errors was trivially fixable, and the fix caused tests to fail because the "fix" introduced escapes to already correct markup. This commit therefore configures Ruff to ignore this lint and does not fix any code that triggers it. Other changes are due to other formatting and linting changes from recent releases of Ruff. Ruff 0.10.0: https://github.com/astral-sh/ruff/releases/tag/0.10.0 Lint S704: https://docs.astral.sh/ruff/rules/unsafe-markup-use/
Configuration menu - View commit details
-
Copy full SHA for 0bc4799 - Browse repository at this point
Copy the full SHA 0bc4799View commit details -
fix: Ignore invalid inventory lines
Previously, inventory items whose `dispname` value contains multiple lines would prevent mkdocstrings from loading the whole inventory file. This change makes mkdocstrings ignore invalid lines in inventories so that the rest of the inventory can still be loaded. This continuation line behavior can be seen in the wild in the OpenEye toolkits inventory file and a few Open Force Field inventory files. These projects' inventories cannot be used with mkdocstrings because of the raised error. Note that in Sphinx too, these inventory files are read succesfully, and the continuation lines are discarded, truncating the display name. In theory, a continuation line that by chance did parse correctly would be interpreted by both packages as a new inventory item. OpenEye Toolkits inventory file: https://docs.eyesopen.com/toolkits/python/objects.inv Open Force Field Toolkit inventory file: https://docs.openforcefield.org/projects/toolkit/en/stable/objects.inv BespokeFit inventory file: https://docs.openforcefield.org/projects/bespokefit/en/stable/objects.inv
Configuration menu - View commit details
-
Copy full SHA for 81caff5 - Browse repository at this point
Copy the full SHA 81caff5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1a98040 - Browse repository at this point
Copy the full SHA 1a98040View commit details -
Configuration menu - View commit details
-
Copy full SHA for df4e7c8 - Browse repository at this point
Copy the full SHA df4e7c8View 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 0.29.0...0.29.1