Warn people away from PyModule_GetDict(), but not too strongly.

(The real issue is whether modules can benefit from an alternate
implementation strategy rather than using a dictionary.  We should migrate
away from direct dictionary manipulation to allow more room for Jeremy to
flex the implementation with changes in globals lookup.)

diff --git a/Doc/api/concrete.tex b/Doc/api/concrete.tex
index f175ff12d7e1725ffd098d98a40a1330bb88e791..976292468d32d47b130d5a321600aa677f1c43ed 100644 (file)
--- a/Doc/api/concrete.tex
+++ b/Doc/api/concrete.tex
@@ -2111,6 +2111,9 @@ There are only a few functions special to module objects.
   namespace; this object is the same as the \member{__dict__}
   attribute of the module object.  This function never fails.
   \withsubitem{(module attribute)}{\ttindex{__dict__}}
+  It is recommended extensions use other \cfunction{PyModule_*()}
+  and \cfunction{PyObject_*()} functions rather than directly
+  manipulate a module's \member{__dict__}.
 \end{cfuncdesc}
 
 \begin{cfuncdesc}{char*}{PyModule_GetName}{PyObject *module}