Platform: Windows XP SP2
Python Version: 2.4.2 final

First off, I'm not sure if this is the same bug as
947380 . Comments say it was fixed in Python 2.4, but
I'm running Python 2.4.2 and it looks like I'm hitting
the same issue. If this is the same issue and has been
fixed in a later version, I apologize.

To reproduce:

1. Create a new directory (e.g., 'foo').
2. Inside foo, create a __init__.py along with a
directory called 'stat' which also has an empty
__init__.py inside of it.
3. 'cd' to this directory via the command line and
start the Python interpreter.

Observe the 'import site' failed error. A quick check
at sys.path reveals that sys.path is munged and doesn't
contain all that it should.

WORKAROUND: Rename 'stat' directory to 'stats' or
something else.

Reproduced on trunk, needed unsetting PYTHONPATH. A test case with
os.mkdir, chdir, etc. would be great.

I can't reproduce this. Closing as out of date. Plus having an import
fail because you shadow a built-in is not a bug.