From f9211e3c372edf996ca7ac040f7351114283d598 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Brigitta=20Sip=C5=91cz?= <b.sipocz@gmail.com>
Date: Sat, 16 Nov 2024 06:12:03 -0800
Subject: [PATCH] DOC: Add back IGNORE_OUTPUTS

---
 docs/registry/index.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/registry/index.rst b/docs/registry/index.rst
index 521d12eb..bcc95063 100644
--- a/docs/registry/index.rst
+++ b/docs/registry/index.rst
@@ -158,7 +158,7 @@ And to look for tap resources *in* a specific cone, you would do
 
   >>> from astropy.coordinates import SkyCoord
   >>> registry.search(registry.Freetext("Wolf-Rayet"),
-  ...                 registry.Spatial((SkyCoord("23d +3d"), 3), intersect="enclosed"))
+  ...                 registry.Spatial((SkyCoord("23d +3d"), 3), intersect="enclosed"))  # doctest: +IGNORE_OUTPUT
   <DALResultsTable length=3>
                  ivoid                ...
                                       ...
@@ -174,7 +174,7 @@ Astropy Quantities are also supported for the radius angle of a SkyCoord-defined
 
   >>> from astropy import units as u
   >>> registry.search(registry.Freetext("Wolf-Rayet"),
-  ...                 registry.Spatial((SkyCoord("23d +3d"), 180*u.Unit('arcmin')), intersect="enclosed"))
+  ...                 registry.Spatial((SkyCoord("23d +3d"), 180*u.Unit('arcmin')), intersect="enclosed"))  # doctest: +IGNORE_OUTPUT
   <DALResultsTable length=3>
                  ivoid                ...
                                       ...