Skip to content
Permalink
Browse files
Fix list formatting
  • Loading branch information
nyalldawson committed Jun 10, 2021
1 parent 49e48f9 commit 7b193334429a326c04b26be8e7c537b43c04002a
Showing with 3 additions and 9 deletions.
  1. +1 −4 python/core/auto_generated/qgspointxy.sip.in
  2. +1 −1 scripts/astyle_all.sh
  3. +1 −4 src/core/qgspointxy.h
@@ -33,10 +33,7 @@ Some valid use cases for :py:class:`QgsPointXY` include:

Use cases for which :py:class:`QgsPointXY` is NOT a valid choice include:

- Storage of coordinates for a geometry. Since :py:class:`QgsPointXY` is strictly 2-dimensional

it should never be used to store coordinates for vector geometries, as this will involve
a loss of any z or m values present in the geometry.
- Storage of coordinates for a geometry. Since :py:class:`QgsPointXY` is strictly 2-dimensional it should never be used to store coordinates for vector geometries, as this will involve a loss of any z or m values present in the geometry.

.. seealso:: :py:class:`QgsPoint`

@@ -34,7 +34,7 @@ find python src tests -type f -print | while read -r f; do
fi

echo -ne "Reformatting $f $elcr"
astyle.sh "$f" || true &
astyle.sh "$f" || true
done

remove_temporary_files.sh
@@ -50,10 +50,7 @@ class QgsPoint;
*
* Use cases for which QgsPointXY is NOT a valid choice include:
*
* - Storage of coordinates for a geometry. Since QgsPointXY is strictly 2-dimensional
*
* it should never be used to store coordinates for vector geometries, as this will involve
* a loss of any z or m values present in the geometry.
* - Storage of coordinates for a geometry. Since QgsPointXY is strictly 2-dimensional it should never be used to store coordinates for vector geometries, as this will involve a loss of any z or m values present in the geometry.
*
* \see QgsPoint
* \since QGIS 3.0

0 comments on commit 7b19333

Please sign in to comment.