Amaury Forgeot d Arc <[email protected]> added the comment: Yes, this is a deliberate feature of pypy: http://doc.pypy.org/en/latest/config/objspace.lonepycfiles.html """ [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 .pyc. ---------- nosy: +amaury status: unread -> wontfix ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1401> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
