[pypy-issue] [issue1401] ImportError: No module named ...

Amaury Forgeot d Arc tracker at bugs.pypy.org
Mon Feb 18 12:02:59 CET 2013

Amaury Forgeot d Arc <amauryfa at gmail.com> added the comment:

Yes, this is a deliberate feature of pypy:
[importing lone .pyc files] is a common cause of issues: most typically, the x.py file is removed 
(manually or by a version control system) but the x module remains accidentally importable because 
the x.pyc file stays around.

Note that this has been removed from the 3.2 version of pypy: since Python3 puts .pyc files in a 
dedicated __pycache__ directory and always checks for the presence of a .py file in the normal place, 
the argument above does not stand anymore.
In Python3, a .pyc file deliberately put in a PYTHONPATH directory cannot be confused with a compiled 

nosy: +amaury
status: unread -> wontfix

PyPy bug tracker <tracker at bugs.pypy.org>

More information about the pypy-issue mailing list