Use and document safe_globals.

README.rst

@@ -47,14 +47,14 @@ This example directly executed in Python could harm your system.
 .. code-block:: pycon
 
     >>> from RestrictedPython import compile_restricted
-    >>> from RestrictedPython import safe_builtins
+    >>> from RestrictedPython import safe_globals
     >>>
     >>> source_code = """
     ... import os
     ...
     ... os.listdir('/')
     ... """
     >>> byte_code = compile_restricted(source_code, '<inline>', 'exec')
-    >>> exec(byte_code, {'__builtins__': safe_builtins}, {})
+    >>> exec(byte_code, safe_globals, {})
     Traceback (most recent call last):
     ImportError: __import__ not found

docs/upgrade_dependencies/index.rst

@@ -28,6 +28,7 @@ RestrictedPython did move some of the imports to the base namespace, so you shou
 
 * predefined built-ins:
 
+  * ``from RestrictedPython import safe_globals``
   * ``from RestrictedPython import safe_builtins``
   * ``from RestrictedPython import limited_builtins``
   * ``from RestrictedPython import utility_builtins``

docs/usage/api.rst

@@ -130,6 +130,7 @@ RestrictedPython has tree major scopes:
 
 2. restricted builtins
 
+  * ``safe_globals``
   * ``safe_builtins``
   * ``limited_builtins``
   * ``utility_builtins``

docs/usage/basic_usage.rst

@@ -86,12 +86,15 @@ So you normally end up using:
             filename='<inline code>',
             mode='exec'
         )
-        exec(byte_code, safe_builtins, None)
+        exec(byte_code, {'__builtins__': safe_builtins}, None)
     except SyntaxError as e:
         pass
 
 One common advanced usage would be to define an own restricted builtin dictionary.
 
+There is a shortcut for ``{'__builtins__': safe_builtins}`` named
+``safe_globals`` which can be imported from ``RestrictedPython``.
+
 Necessary setup
 ---------------