Doc: Clarify del statement doc

[adorilson]

Documentation

The del statement doc says:

Deletion of a name removes the binding of that name from the local or global namespace, depending on whether the name occurs in a global statement in the same code block.
If the name is unbound, a NameError exception will be raised.

The last sentence is confusing; it could be better, something like

If you access an unbound name, an exception NameError will be raised.

Linked PRs

• gh-138871: Clarify NameError exception in 'del' #138881
• [3.14] gh-138871: Clarify NameError exception in 'del' (GH-138881) #138903
• [3.13] gh-138871: Clarify NameError exception in 'del' (GH-138881) #138904

[brianschubert]

I think the current wording is clearer. "The" makes it clear that it's referencing the name from the previous sentence (i.e. the name being deleted with del). Saying "If you access an unbound name" could be misinterpreted as talking about using a name after it's been deleted.

Also, "a NameError exception" is more grammatical than "an exception NameError".

[adorilson]

Saying "If you access an unbound name" could be misinterpreted as talking about using a name after it's been deleted.

It is precisely what I think can be clarified. The exception is raised just when trying to access an unbound name, not when a del name is successfully executed. Or...

Do you refer to a del against an unbound name? I've just realized that del raises a NameError in that situation.
Is the sentence about this situation? In this case, the sentence could be:

If the name is unbound, `del` will raise a NameError exception.

Also, "a NameError exception" is more grammatical than "an exception NameError".

Sorry. It's just an initial idea.

[terryjreedy]

Issues are for discussing alternatives and details before a PR is made. On quick reading, I did not get that the sentence was about deleting an unbound name as opposed to accessing a deleted name later. How about "Trying to delete an unbound name raises a NameError exception."

[adorilson]

I did not get that the sentence was about deleting an unbound name as opposed to accessing a deleted name later.

Now, I accept both interpretations, which endorses the need for improvement.

How about "Trying to delete an unbound name raises a NameError exception."

I think it is this. Because it is talking about del. Access is another operation.

[alexeev-prog]

Hello, I've read the discussion and I agree that the suggested change by @terryjreedy clarifies the documentation. The phrase "Trying to delete an unbound name raises a NameError exception." is clear and unambiguous.

I would like to work on this issue and make the necessary change in the documentation. Could you please guide me on which file exactly needs to be modified?

[adorilson]

I would like to work on this issue and make the necessary change in the documentation. Could you please guide me on which file exactly needs to be modified?

This paragraph

cpython/Doc/reference/simple_stmts.rst

Line 466 in 7168e98

Deletion of a name removes the binding of that name from the local or global