@@ -108,8 +108,8 @@ in asynchronous generators:
1081082. https://discuss.python.org/t/47050
1091093. https://discuss.python.org/t/66886
110110
111- Additionally, this design decision has ` come up
112- <https://stackoverflow.com/questions/47376408> `__ on Stack Overflow.
111+ Additionally, users have ` questioned < https://stackoverflow.com/questions/47376408 >`__
112+ this design decision on Stack Overflow.
113113
114114
115115Subgenerator delegation is useful for asynchronous generators
@@ -122,11 +122,11 @@ item. This comes with a few drawbacks:
1221221. It obscures the intent of the code and increases the amount of effort
123123 necessary to work with asynchronous generators, because each delegation
124124 point becomes a loop. This damages the power of asynchronous generators.
125- 2. :meth: `~agen.asend `, :meth: `~agen.athrow `, and :meth: `~agen.aclose `,
125+ 2. :meth: `~agen.asend `, :meth: `~agen.athrow `, and :meth: `~agen.aclose `
126126 do not interact properly with the caller. This is the primary reason that
127127 ``yield from `` was added in the first place.
1281283. Return values are not natively supported with asynchronous generators. The
129- workaround for this it to raise an exception, which increases boilerplate.
129+ workaround for this is to raise an exception, which increases boilerplate.
130130
131131
132132Specification
0 commit comments