Repository navigation
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/python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1670ecb
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: mkdocstrings/python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 624974a
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 14 files changed
- 5 contributors
Commits on Jul 8, 2026
-
chore: Update sponsors section in README (#332)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 0fa2d2e - Browse repository at this point
Copy the full SHA 0fa2d2eView commit details
Commits on Aug 7, 2026
-
fix: Increase stash key length from 1 to 2
Cross-reference stash keys start with `_` and preserve the rendered identifier length. One-character and two-character identifiers therefore share a keyspace of only 62 keys. Once all keys are present, `_gen_stash_key` retries random choices forever. This happens for example in mkdocstrings when rendering an attribute value that has 62 names in it or more. We increase the minimum key length by 1, to reach a keyspace of 3844, making it very unlikely to hit the limit again. PR-336: #336
Configuration menu - View commit details
-
Copy full SHA for 6ff2749 - Browse repository at this point
Copy the full SHA 6ff2749View commit details
Commits on Aug 16, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 4b38b6b - Browse repository at this point
Copy the full SHA 4b38b6bView commit details -
Configuration menu - View commit details
-
Copy full SHA for bb49b15 - Browse repository at this point
Copy the full SHA bb49b15View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3c782f5 - Browse repository at this point
Copy the full SHA 3c782f5View commit details -
Configuration menu - View commit details
-
Copy full SHA for a025f49 - Browse repository at this point
Copy the full SHA a025f49View commit details
Commits on Aug 17, 2026
-
fix: Don't render environment paths in source block labels
When an object's file lives in a virtual environment inside the current working directory (for example a pydantic `BaseModel` subclass documented with `preload_modules: [pydantic]` and an in-project `.venv`), source blocks were labeled with the environment path, like `.venv/lib/python3.10/site-packages/pydantic/main.py`. The path is relative to the current working directory, so it slipped past the `is_absolute()` check that normally keeps environment paths out of rendered docs. Add a `source_location` filter that strips everything up to and including a `site-packages` directory from displayed source paths, and use it for every source block label: merged `__init__`, class, and function, in both themes. Centralizing the logic also fixes the label for single-file modules installed directly in `site-packages` (like `six.py`), whose package-relative path still contained the environment directory. Labels of objects belonging to the documented package itself are unchanged. Issue-333: #333 PR-338: #338
Configuration menu - View commit details
-
Copy full SHA for 84ba73e - Browse repository at this point
Copy the full SHA 84ba73eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 624974a - Browse repository at this point
Copy the full SHA 624974aView 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 1670ecb...624974a