Merged revisions 78297,78308 via svnmerge from

svn+ssh://pythondev@svn.python.org/python/trunk

........
  r78297 | andrew.kuchling | 2010-02-22 03:29:10 +0100 (Mo, 22 Feb 2010) | 1 line

  #7076: mention SystemRandom class near start of the module docs; reword change description for clarity.  Noted by Shawn Ligocki.
........
  r78308 | andrew.kuchling | 2010-02-22 16:13:17 +0100 (Mo, 22 Feb 2010) | 2 lines

  #6414: clarify description of processor endianness.
  Text by Alexey Shamrin; I changed 'DEC Alpha' to the more relevant 'Intel Itanium'.
........

Doc/library/random.rst

@@ -52,7 +52,11 @@ known to fail some stringent randomness tests.  See the references below for a
 recent variant that repairs these flaws.
 
 .. versionchanged:: 2.3
-   Substituted MersenneTwister for Wichmann-Hill.
+   MersenneTwister replaced Wichmann-Hill as the default generator.
+
+The :mod:`random` module also provides the :class:`SystemRandom` class which
+uses the system function :func:`os.urandom` to generate random numbers
+from sources provided by the operating system.
 
 Bookkeeping functions:
 

Doc/library/struct.rst

@@ -187,9 +187,11 @@ following table:
 
 If the first character is not one of these, ``'@'`` is assumed.
 
-Native byte order is big-endian or little-endian, depending on the host system.
-For example, Motorola and Sun processors are big-endian; Intel and DEC
-processors are little-endian.
+Native byte order is big-endian or little-endian, depending on the host
+system. For example, Intel x86 and AMD64 (x86-64) are little-endian;
+Motorola 68000 and PowerPC G5 are big-endian; ARM and Intel Itanium feature
+switchable endianness (bi-endian). Use ``sys.byteorder`` to check the
+endianness of your system.
 
 Native size and alignment are determined using the C compiler's
 ``sizeof`` expression.  This is always combined with native byte order.