sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-10-04 00:04:03 -04:00
Code Issues Packages Projects Releases Wiki Activity

[sipify] Strip \ref tags

Browse Source
This commit is contained in:
Nyall Dawson 2025-04-02 10:40:23 +10:00
parent 8565a63e1a
commit d4027f3c09
3 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
python/PyQt6/core/auto_generated/proj/qgscoordinatereferencesystem.sip.in
View File

@ -46,10 +46,9 @@ representation that will be ultimately used.
Methods that allow inspection of CRS instances include
:py:func:`~isValid`, :py:func:`~authid`, :py:func:`~description`,
:py:func:`~toWkt`, :py:func:`~toProj`, :py:func:`~mapUnits` and others.
Creation of CRS instances is further described in \ref
crs_construct_and_copy section below. Transformations between coordinate
reference systems are done using :py:class:`QgsCoordinateTransform`
class.
Creation of CRS instances is further described in crs_construct_and_copy
section below. Transformations between coordinate reference systems are
done using :py:class:`QgsCoordinateTransform` class.
For example, the following code will create and inspect "British
national grid" CRS:
@ -145,7 +144,7 @@ features a GUI for management of local custom CRS definitions.
There are therefore two databases: one for shipped CRS definitions and
one for custom CRS definitions. Custom CRS have internal IDs (accessible
with :py:func:`~srsid`) greater or equal to \ref
with :py:func:`~srsid`) greater or equal to
:py:class:`Qgis`.USER_CRS_START_ID. The local CRS databases should never
be accessed directly with SQLite functions, instead you should use
:py:class:`QgsCoordinateReferenceSystem` API for CRS lookups and for

9
python/core/auto_generated/proj/qgscoordinatereferencesystem.sip.in
View File

@ -46,10 +46,9 @@ representation that will be ultimately used.
Methods that allow inspection of CRS instances include
:py:func:`~isValid`, :py:func:`~authid`, :py:func:`~description`,
:py:func:`~toWkt`, :py:func:`~toProj`, :py:func:`~mapUnits` and others.
Creation of CRS instances is further described in \ref
crs_construct_and_copy section below. Transformations between coordinate
reference systems are done using :py:class:`QgsCoordinateTransform`
class.
Creation of CRS instances is further described in crs_construct_and_copy
section below. Transformations between coordinate reference systems are
done using :py:class:`QgsCoordinateTransform` class.
For example, the following code will create and inspect "British
national grid" CRS:
@ -145,7 +144,7 @@ features a GUI for management of local custom CRS definitions.
There are therefore two databases: one for shipped CRS definitions and
one for custom CRS definitions. Custom CRS have internal IDs (accessible
with :py:func:`~srsid`) greater or equal to \ref
with :py:func:`~srsid`) greater or equal to
:py:class:`Qgis`.USER_CRS_START_ID. The local CRS databases should never
be accessed directly with SQLite functions, instead you should use
:py:class:`QgsCoordinateReferenceSystem` API for CRS lookups and for

1
scripts/sipify.py
View File

@ -813,6 +813,7 @@ def process_doxygen_line(line: str) -> str:
# Remove prepending spaces and apply various replacements
line = re.sub(r"^\s+", "", line)
line = re.sub(r"\\a (.+?)\b", r"``\1``", line)
line = re.sub(r" \\ref\b", "", line)
line = line.replace("::", ".")
line = re.sub(r"\bnullptr\b", "None", line)