Author: Tristan Arthur <[email protected]>
Branch: TreeStain/main-lines-changed-in-l77-l83-made-para-1484471558033
Changeset: r89579:f7e0e9cfbf80
Date: 2017-01-15 09:13 +0000
http://bitbucket.org/pypy/pypy/changeset/f7e0e9cfbf80/
Log: Main lines changed in L77 - L83. Made paragraph more
cohesive/flowing.
diff --git a/pypy/doc/faq.rst b/pypy/doc/faq.rst
--- a/pypy/doc/faq.rst
+++ b/pypy/doc/faq.rst
@@ -32,10 +32,10 @@
standard library.
The language features (including builtin types and functions) are very
-complete and well tested, so if your project does not use many
+refined and well tested, so if your project doesn't use many
extension modules there is a good chance that it will work with PyPy.
-We list the differences we know about in :doc:`cpython differences
<cpython_differences>`.
+We list the known differences in :doc:`cpython differences
<cpython_differences>`.
Module xyz does not work with PyPy: ImportError
@@ -76,9 +76,9 @@
You cannot import *any* extension module in a `sandboxed PyPy`_,
sorry. Even the built-in modules available are very limited.
-Sandboxing in PyPy is a good proof of concept, really safe IMHO, but
-it is only a proof of concept. It seriously requires someone working
-on it. Before this occurs, it can only be used it for "pure Python"
+Sandboxing in PyPy is a good proof of concept, and is without a doubt
+safe IMHO, however it is only a proof of concept. It currently requires
+some work and in the meantime, can only be used for "pure Python"
examples: programs that import mostly nothing (or only pure Python
modules, recursively).
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
