bpo-40899: Document exception raised when module cannot be imported

[dukecat0]

https://bugs.python.org/issue40899

[ambv]

1. Note Ronald's comment on arbitrary exceptions being raised from a module body while it's being imported.
2. Please don't insert error handling information in the leading paragraph. Look at other functions in functions.rst, they have exception information listed further in the text, usually as the last paragraph describing them.

[gpshead]

1. Note Ronald's comment on arbitrary exceptions being raised from a module body while it's being imported.
2. Please don't insert error handling information in the leading paragraph. Look at other functions in functions.rst, they have exception information listed further in the text, usually as the last paragraph describing them.

while I've Approved this change from the standpoint of not being a bad thing to document, I do think the above should be addressed first.

[github-actions]

This PR is stale because it has been open for 30 days with no activity.

[iritkatriel]

@meowmeowmeowcat This has been awaiting changes for over a year. Are you planning to finish this or shall we close it so someone else can pick it up?

[iritkatriel]

See #27709 (comment).

[dukecat0]

Are you planning to finish this or shall we close it so someone else can pick it up?

I am going to finish this. Sorry for the late response!

I have made the requested changes; please review again

[iritkatriel]

I'm not sure I like this wording - what do you mean "can be raised", it sounds like it is possible for import to fail and not raise an exception.

[dukecat0]

Note Ronald's comment on arbitrary exceptions being raised from a module body while it's being imported.

It means arbitrary exceptions can also be raised.

[iritkatriel]

I understand the intent, but I don't think that's the only possible interpretation of the current wording.

[dukecat0]

I just found out that #94662 is also doing the same thing. Would you prefer that one?