I can reference code from a notebook using

.. literalinclude:: ../auto_examples/plot_myscript.py
    :start-after: [some-tag]
    :end-before: [another-tag]

and the resulting images using

.. figure:: ../auto_examples/images/sphx_glr_plot_myscript_001.png
    :target: ../auto_examples/plot_myscript.html

However, it doesn't seem to be possible to reference output from code that's part of a sphinx-gallery. This would be very useful.

I did find the following in the generated .rst file:

.. rst-class:: sphx-glr-script-out

 Out:

 .. code-block:: none

    <the output>

Perhaps if we had a dedicated output file (which we do for images) it would be possible? Thanks for considering!

Update: I found a way to hack this together in the meanwhile, but I don't particularly like it. One of the output files is the .rst file which includes printed output. I added the following code to my plotting python script

output_marker = "OUTPUT_"
print(f"[{output_marker}_START]")
<code with interesting output that I want to show elsewhere goes here>
print(f"[{output_marker}_END]")

[Amazingly, the separation of the string is necessary, otherwise literalinclude below will show the code, not the output!]

... and then simply add the following where you show the code:

.. literalinclude:: auto_examples/plot_myscript.rst
   :start-after: [OUTPUT_START]
   :end-before: [OUTPUT_END]

Reasons why I don't like this:

• The example code gets polluted with the output marker code.
• The output could change from build to build without me noticing. Doctest solves this nicely, but if I want to use the same code snippet in several place I have to duplicate it every time. That's why I thought of creating an example and using literalinclude instead in the first place.