I just noticed that distutils creates an egg-info for the stdlib while installing Python.

This definitely happens for Python 2.7 and Python 3.2 (both framework builds on OSX).

In lib-dynload there is and egg-info file: "Python-2.7.1-py2.7.egg-info" 

Is this intentional? 

If it is: the OSX installer does not remove older versions when installing an upgrade (that is, I also have egg-info files for Python-2.7 and several pre-releases)

I think the existence of this file is intentional, to satisfy pkg_resources requirements for “Python”.  Philip can confirm.

After a bit of exploring, I think that it’s possible that the existence of this file is not intentional.  Python uses distutils.core.setup to build install most of its own extension modules, and the PyBuildInstall class used for the install command does not disable the automatic egg-info generation.

With the move of packaging into the stdlib and the addition of the superseding dist-info format, such files can be removed in 3.3.  They’re harmless in stable versions, and removing them would require updates to the build tools that don’t really bring us anything.

+1 to removing of the spurious egg-info files. For the folks who are not aware of the multitude 'packaging terms', egg-info files are the first step towards the path leading to more confusion. 
So cleaning up would be definitely better in the standard distribution.

I agree that the egg-info file should be removed in 3.3, especially because distutils2 has a better way of specifying python version dependencies.

The OSX installers for 2.7, 3.1 and 3.2 should remove the egg-info file for older releases, that way we at least don't lie about the version.

IMO we cannot remove the egg-info for current releases, someone might depend on their existence and this is a minor enough nit to not risk breaking code.

Yes, I only target 3.3.

The egg-info file for Python itself can go, but what about wsgiref.egg-info?  It was included in 2.5 too to preserve compatibility with code using pkg_resources.require instead of regular import.  I’d like to remove it too: it’s not needed anymore with the new standards, and I don’t think there’s a backward compat issue.  There shouldn’t be 3.x code out there using this call, since all 3.x versions have had wsgiref in the stdlib.  The only compat issue could be for some 2.x codebase relying on the egg-info file and being converted to Python 3.3: if we remove the file, people would have to remove the pkg_resources.require call.  I would argue in favor of the removal: people can assume that wsgiref is in the stdlib if they target 2.5+ or 3.x, and if they do use the require call, then removing it is just another tiny step in the conversion process.

I am going to remove wsgiref.egg-info

see issue12218

New changeset e3f6c10eb590 by Éric Araujo in branch 'default':
Stop creating a Python-X.Y.Z-pyX.Y.egg-info file on install (#10645)
http://hg.python.org/cpython/rev/e3f6c10eb590

New changeset af7bc95e5b1e by Éric Araujo in branch 'default':
The change done for #10645 deserves a NEWS entry
http://hg.python.org/cpython/rev/af7bc95e5b1e