| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Current (https://docs.python.org/3/library/os.html#os.PathLike.__fspath__): Proposed (https://cpython-previews--129311.org.readthedocs.build/en/129311/library/os.html#os.PathLike.__fspath__): A |
Sorry, something went wrong.
|
Hrm... I weakly prefer the current rendering. The PyAbstractMethod class in pyspecific.py doesn't seem like that much of a maintenance burden here? |
Sorry, something went wrong.
|
I suppose it's more of a design point than a question of maintenance burden. Sphinx's default Python domain should be good enough to document the Python documentation mostly using defaults. We will have some custom logic (e.g. for pydoc, or Misc/NEWS), but when documenting pure-Python objects, I would to get to a point where we don't patch Sphinx. This is very likely to involve upstream changes though (made easier by the fact we now have decoupled our version support from downstream Linux distros). Is your preference to show e.g. "abstract method __fspath__()"? For methods in general we don't show the method prefix, but we could make an exception here? A |
Sorry, something went wrong.
Referring to it as "abstractmethod" or "abstract method" rather than simply "abstract" does make sense to me, because the decorator is abc.abstractmethod (not abc.abstract). Also, the decorator doesn't have any effect if you apply it to a non-method, so I'm not sure what an abstract non-method function would look like! |
Sorry, something went wrong.
|
I've opened sphinx-doc/sphinx#13271 on the Sphinx side. The three options we have are (1) keeping abstract, (2) using abstractmethod, or (3) using abstract method. The third has some symmetry with abstract properties, which are currently documented as abstract property. A |
Sorry, something went wrong.
# Conflicts: # Doc/tools/extensions/pyspecific.py
|
Thanks @AA-Turner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
Sorry, something went wrong.
|
Sorry, @AA-Turner, I could not cleanly backport this to 3.13 due to a conflict. cherry_picker 30e892473e0dfe5c3fecabcaac420cefe45e2ed4 3.13 |
Sorry, something went wrong.
|
Sorry, @AA-Turner, I could not cleanly backport this to 3.12 due to a conflict. cherry_picker 30e892473e0dfe5c3fecabcaac420cefe45e2ed4 3.12 |
Sorry, something went wrong.
…:abstract:`` option (python#129311) (cherry picked from commit 30e8924)
… the ``:abstract:`` option (pythonGH-129311) (cherry picked from commit 30e8924) Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
|
GH-130440 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
|
GH-130439 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This removes our custom .. abstractmethod:: directive in favour of Sphinx's :abstractmethod: directive option. There is a minor change to rendered output, which I will paste in a comment below.
A
📚 Documentation preview 📚: https://cpython-previews--129311.org.readthedocs.build/