[pypy-svn] r56584 - pypy/dist/pypy/doc/config

arigo at codespeak.net arigo at codespeak.net
Wed Jul 16 01:19:35 CEST 2008

Author: arigo
Date: Wed Jul 16 01:19:33 2008
New Revision: 56584

   pypy/dist/pypy/doc/config/objspace.lonepycfiles.txt   (contents, props changed)
Document the pyc files options.

Added: pypy/dist/pypy/doc/config/objspace.lonepycfiles.txt
--- (empty file)
+++ pypy/dist/pypy/doc/config/objspace.lonepycfiles.txt	Wed Jul 16 01:19:33 2008
@@ -0,0 +1,16 @@
+If turned on, PyPy accepts to import a module ``x`` if it finds a
+file ``x.pyc`` even if there is no file ``x.py``.
+This is the way that CPython behaves, but it is disabled by
+default for PyPy because it 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
+The usual reason for wanting this feature is to distribute
+non-open-source Python programs by distributing ``pyc`` files
+only, but this use case is not practical for PyPy at the
+moment because multiple versions of PyPy compiled with various
+optimizations might be unable to load each other's ``pyc``

Modified: pypy/dist/pypy/doc/config/objspace.usepycfiles.txt
--- pypy/dist/pypy/doc/config/objspace.usepycfiles.txt	(original)
+++ pypy/dist/pypy/doc/config/objspace.usepycfiles.txt	Wed Jul 16 01:19:33 2008
@@ -1,4 +1,4 @@
 If this option is used, then PyPy imports and generates "pyc" files in the
-usual way. This is mostly always on,
-except when using other options that lead to PyPy-specific bytecodes that should
-not be cached on disk because they might confuse CPython.
+same way as CPython.  This is true by default and there is not much reason
+to turn it off nowadays.  If off, PyPy never produces "pyc" files and
+ignores any "pyc" file that might already be present.

More information about the Pypy-commit mailing list