The raise expression [here](https://github.com/python/cpython/blob/ad442a674ca443feec43a88a2d3671784712e550/Lib/tempfile.py#L826) isn't valid, since it isn't in an except block.

It'll still raise, given it's invalid, though not with the exception it should be raising with...

I think this diff will fix it, I can put this in as a PR if that's reasonable. Though I'm not sure how to test it — we need to generate an error that's not covered by the existing cases. 

```diff

diff --git a/Lib/tempfile.py b/Lib/tempfile.py
index efcf7a7fb3..227e25d0fc 100644
--- a/Lib/tempfile.py
+++ b/Lib/tempfile.py
@@ -823,7 +823,7 @@ def resetperms(path):
                 pass
             else:
                 if not ignore_errors:
-                    raise
+                    raise exc_info[1]
 
         _shutil.rmtree(name, onerror=onerror)

```

Adding Serhiy, who added the code in question in commit e9b51c0ad81da1da11ae65840ac8b50a8521373c (GH-10320, bpo-26660, bpo-35144).

> It'll still raise, given it's invalid, though not with the 
> exception it should be raising with...

onerror() is always called to handle an exception, and `raise` will re-raise that exception. Is there a specific case where this isn't working as expected for you?

I see @eryksun — by convention `onerror` is always called in an except block, and so having a bare `raise` outside of an explicit except block is OK.

Thanks for clarifying. I'll close this.