Fix typos detected by Terry Reedy.

This commit is contained in:
Guido van Rossum 2001-07-29 23:25:00 +00:00
parent 3ea05fba23
commit e3f70cd115
1 changed files with 3 additions and 3 deletions

View File

@ -540,7 +540,7 @@ C API
- In the more complicated case, there's a conflict between names - In the more complicated case, there's a conflict between names
stored in the instance dict and names stored in the type dict. stored in the instance dict and names stored in the type dict.
If both dicts have an entry with the same key, which one should If both dicts have an entry with the same key, which one should
we return? Looking as classic Python for guidance, I find we return? Looking at classic Python for guidance, I find
conflicting rules: for class instances, the instance dict conflicting rules: for class instances, the instance dict
overrides the class dict, *except* for the special attributes overrides the class dict, *except* for the special attributes
(like __dict__ and __class__), which have priority over the (like __dict__ and __class__), which have priority over the
@ -555,14 +555,14 @@ C API
2. Look in the instance dict. If you find anything, that's it. 2. Look in the instance dict. If you find anything, that's it.
(This takes care of the requirement that normally the (This takes care of the requirement that normally the
instance dict overrides the class dict. instance dict overrides the class dict.)
3. Look in the type dict again (in reality this uses the saved 3. Look in the type dict again (in reality this uses the saved
result from step 1, of course). If you find a descriptor, result from step 1, of course). If you find a descriptor,
use its get() method; if you find something else, that's it; use its get() method; if you find something else, that's it;
if it's not there, raise AttributeError. if it's not there, raise AttributeError.
This requires a classification of descriptors in data and This requires a classification of descriptors as data and
nondata descriptors. The current implementation quite sensibly nondata descriptors. The current implementation quite sensibly
classifies member and getset descriptors as data (even if they classifies member and getset descriptors as data (even if they
are read-only!) and member descriptors as nondata. are read-only!) and member descriptors as nondata.