Cristian Le
Cristian Le
This is more of a show-and-tell to consider if something similar can be adopted by sphinx. The idea here is to have some helpers to construct and manipulate the `SphinxDirective.content`...
### Describe the bug With the recent support for PEP695, the documentation of module level aliases does not have the docstrings inherited, unlike non-type members, i.e. if we have a...
**Is your feature request related to a problem? Please describe.** `sphinx.ext.autodoc` is used for documenting *only* python objects, and that is perfectly fine. With the recent refactoring, it is a...
**Is your feature request related to a problem? Please describe.** Currently the [Developing autodoc extensions](https://www.sphinx-doc.org/en/master/development/tutorials/autodoc_ext.html) is using the legacy interface. It is not clear how one is supposed to do...
**Is your feature request related to a problem? Please describe.** I am working on a sphinx domain where I am getting effectively document sections from another source. For the most...
### What happened? What is the problem? Normally the `%autosetup`/`%setup` macros are overwritten so that it points to the new git archive created by packit. This does not seem to...
## Description In order to support the fine-grained control of how we want to build each components, we should deprecate the usage of `BUILD_SHARED_LIBS` as the cache variable used to...
I think `custom_cxxstandard` and `FindTargetOpenMP` could also be updated, but I wonder if those should be re-evaluated instead. E.g. `custom_cxxstandard` seems to be a backport for cxx20 support, which should...
Looking through the build logic, the build process looks very weird and it does not allow incremental build or reusing of older build artifacts. The suggestion is to separate the...
Upstream has indicated that pydantic v1 will not get python3.14 support. So it might be best to drop the usage of pydantic v1 api usage.