This is an automated email from the ASF dual-hosted git repository.
rok pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/arrow.git
The following commit(s) were added to refs/heads/master by this push:
new cd0d094104 MINOR: [Doc][Python] Fix wording in custom scalar extension
type docs (#13649)
cd0d094104 is described below
commit cd0d094104c5cbba963c3eda026f3747c139f66b
Author: Joris Van den Bossche <[email protected]>
AuthorDate: Tue Jul 19 19:02:42 2022 +0200
MINOR: [Doc][Python] Fix wording in custom scalar extension type docs
(#13649)
Small follow-up on https://github.com/apache/arrow/pull/13594
Authored-by: Joris Van den Bossche <[email protected]>
Signed-off-by: Rok <[email protected]>
---
docs/source/python/extending_types.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/source/python/extending_types.rst
b/docs/source/python/extending_types.rst
index 7e241f6441..9b6743cb10 100644
--- a/docs/source/python/extending_types.rst
+++ b/docs/source/python/extending_types.rst
@@ -290,8 +290,9 @@ Custom scalar conversion
~~~~~~~~~~~~~~~~~~~~~~~~
If you want scalars of your custom extension type to convert to a custom type
when
-:meth:`ExtensionScalar.as_py()` is called, you can override the
:meth:`ExtensionScalar.as_py()` by subclassing :class:`ExtensionScalar`.
-method. For example, if we wanted the above example 3D point type to return a
custom
+:meth:`ExtensionScalar.as_py()` is called, you can override the
+:meth:`ExtensionScalar.as_py()` method by subclassing :class:`ExtensionScalar`.
+For example, if we wanted the above example 3D point type to return a custom
3D point class instead of a list, we would implement::
Point3D = namedtuple("Point3D", ["x", "y", "z"])
