docs: add version compatibility table#733
Conversation
|
All commit authors signed the Contributor License Agreement. |
| * - :class:`Buffer` | ||
| - 3.12 | ||
| - 4.6.0 | ||
| - |
| - 4.15.0 | ||
| - :pep:`800` | ||
| * - :func:`evaluate_forward_ref` | ||
| - |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #733 +/- ##
=======================================
Coverage 97.19% 97.19%
=======================================
Files 3 3
Lines 7815 7815
=======================================
Hits 7596 7596
Misses 219 219
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
I'm happy to finish this up but @r266-tech are you willing to sign the contributor license agreement? Otherwise we'll have to close this PR. |
Add a table listing typing_extensions objects that backport or extend features from the standard library, showing: - Python version when the feature was added to typing - typing_extensions release that first included it - Associated PEP (if any) Closes python#299
r266-tech
force-pushed
the
docs/version-table
branch
from
4ddd22e to
7541a36
Compare
|
@JelleZijlstra CLA signed and check is green now — happy to have you finish it up whenever convenient, thanks! |
|
Addressed both review comments in e16f2ba: added PEP 688 for |
|
The CI failures are unrelated codecov problems. |
|
Hmm, it seems like we don't have a readthedocs preview, and I'm not sure how the docs are build and deployed to readthedocs. |
|
The current CI failures look unrelated to this docs patch/codecov, as noted above. I do not see a per-PR Read the Docs preview configured for this repo; after e16f2ba I verified the docs locally with Sphinx and the compatibility table renders from |
3 participants
Summary
Adds a version compatibility table to the documentation, as requested in #299.
The table lists objects provided by
typing_extensionsthat backport or extend features from the standard library, showing:typingThis follows the format suggested by @JelleZijlstra in the issue discussion, using a
list-tabledirective as recommended by @AlexWaygood for easier maintenance.Closes #299