gh-137337: Clarify import statement namespace binding

[kovan]

Summary

The import statement documentation says names are defined "in the local namespace," which is inaccurate when the imported name has been declared global or nonlocal:

x = None
def f():
    global x
    import os as x  # Assigns to global namespace, not local

Updates two places in Doc/reference/simple_stmts.rst:

• The basic import description (step 2): "local namespace" -> "current namespace... just as an assignment statement would, including global, local, and nonlocal semantics"
• The from ... import description (step 2.d): "local namespace" -> "current namespace"

This follows the wording proposed by @nedbat and discussed with @serhiy-storchaka and @terryjreedy in the issue thread.

Test plan

• make -C Doc check passes
• make -C Doc html passes (no warnings)

🤖 Generated with Claude Code

• Issue: Documentation of import statement should include binding to global and nonlocal namespaces #137337

---

📚 Documentation preview 📚: https://cpython-previews--144607.org.readthedocs.build/

[johnslavik]

Cool!

[johnslavik]

Maybe this would be a little clearer?

Suggested change

	would, including global, local, and nonlocal semantics.
	would (including :keyword:`global` and :keyword:`nonlocal` semantics).

[kovan]

I have made the requested changes; please review again

[bedevere-app]

Thanks for making the requested changes!

@nedbat: please review the changes made to this pull request.

[miss-islington-app]

Thanks @kovan for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖

[bedevere-app]

GH-149369 is a backport of this pull request to the 3.14 branch.

[bedevere-app]

GH-149370 is a backport of this pull request to the 3.13 branch.