existing and mentioned the OSError possibility.

when the user doesn't hold the symbolic link privilege rather than hiding it.

 * Replace "bytes" by "bytes object" in struct error messages
 * Document the API change in What's new in Python 3.2
 * Fix test_wave
 * Remove also ugly implicit conversions in test_struct

#10739: document that on Windows, socket.makefile() does not make a file that has a true file descriptor usable where such a thing is expected.

#10679: install idle, pydoc, 2to3 scripts with X.Y suffix for make altinstall; create symlinks for make install.

Remove confusing paragraph -- this is relevant only to advanced users anyway and does not belong into the tutorial.

Forbidden in C, stupid language!

Function removed by r83195.

PyErr_SetExcFromWindowsErrWithFilename() decode the filename from the
filesystem encoding instead of UTF-8.

encoding instead of UTF-8.

encoding instead of UTF-8.

I've only tested regular runs and -j runs.  If I've broken anything
else I'm sure I'll hear about it sooner or later.

I'm assuming that the putative path from the malformed
pth file is simply not found and therefore ignored.

If a .pth file contained an error, it could cause a traceback in site.py,
terminating its processing.  In 2.7 and 3.2, the interpreter will then not
start.  Previously, a message would print saying to use -v to get the
traceback.  In either case, the traceback generated for a failed .pth file did
not include the .pth filename, making it difficult to debug the problem.  Now
site.py reports not only the .pth filename but also the line number causing the
error, and just skips the remainder of the file.