homepage

the documentation for generator.throw() does not mention the fact that it has the same semantics for the three arguments as a "raise" expression has.
The first two arguments can be:
throw(exc_type, None)
throw(exc_type, value)
throw(exc_type, exc_instance)
throw(exc_instance, None)

Kristjan, can you write a patch for this?

Here's one for 2.7. I'm still looking at 3. The funny thing is that the signature of generator.throw reflects 2.x conventions. I'm figuring out if it can be used with the .with_traceback() idiom

And 3.x

I like the patches, except the example in 3x.diff. Please see the review.

Note that the docstring does not match the doc:
PyDoc_STRVAR(throw_doc,
"throw(typ[,val[,tb]]) -> raise exception in generator,\n\
return next yielded value or raise StopIteration.");
Should I change the docstring too?

See Issue 13213 for some analysis of the behaviour of different combinations of arguments.
The docstring should be changed if necessary, but in this case I don’t see what needs changing. The argument names perhaps, just for consistency’s sake?

I can’t really comment on the 2.7 version, because I’m not too familiar with Python 2 exceptions.
For Python 3, is there any reason to bless the None, tuple or non-exception cases as the exception "value" argument? IMO these just make things too complicated without any benefit. Changes I would make to the patch:
* Only mention that "value" can be omitted, or it can be an instance of the class specified by "type". Drop mentioning the None option, and the single or tuple constructor argument options. It looks like the tuple option actually gets expanded to multiple constructor arguments?!
* Mention that if "value" is passed, its traceback could be lost
* Drop the example, unless someone can come up with a concise and realistic example
* Unify with definition for coroutines <https://docs.python.org/dev/reference/datamodel.html#coroutine.throw>
* Change the doc string(s) to match the argument names, but don’t bother copying the full definition text

Changes in throw-3x.v2.patch:
* Split into two signatures
* Added parallel coroutine.throw(value) signature
* *Value* should be an exception instance; drop mentioning other options
* Default value is instantiated from *type*
* __traceback__ can be cleared
* Dropped the example
* Update generator and coroutine doc strings with double signatures

Martin, could you please rebase your patch on top of recent cpython default branch, so that a 'review' link appears?

This one is based on the public 3.5 branch, so should work. I corrected a small typo made in the previous patch.

It seems that this patch was close to being merged. Would it be helpful for me to create a PR for it over 3.8? Thanks!

This still hasn't been fixed. I suspect that a new patch should be produced and uploaded as a PR. It looks pretty simple.

New changeset 8be7c2bc5ad5e295f0f855bb31db412eef2c7c92 by Dave Goncalves in branch 'main':
bpo-14911: Corrected generator.throw() documentation (GH-32207)
https://github.com/python/cpython/commit/8be7c2bc5ad5e295f0f855bb31db412eef2c7c92

New changeset 625f6704c0d783360574bbab2f78b0b9bbed5891 by Miss Islington (bot) in branch '3.10':
bpo-14911: Corrected generator.throw() documentation (GH-32207)
https://github.com/python/cpython/commit/625f6704c0d783360574bbab2f78b0b9bbed5891

New changeset 98d57737de73342d33d1b90dc0285f586465d22b by Miss Islington (bot) in branch '3.9':
bpo-14911: Corrected generator.throw() documentation (GH-32207)
https://github.com/python/cpython/commit/98d57737de73342d33d1b90dc0285f586465d22b