Author: Alex Gaynor <alex.gay...@gmail.com>
Branch: extradoc
Changeset: r5102:e2ad4c53afac
Date: 2013-10-25 16:21 -0700
http://bitbucket.org/pypy/extradoc/changeset/e2ad4c53afac/

Log:    fancy dash

diff --git a/blog/draft/coverage.rst b/blog/draft/coverage.rst
--- a/blog/draft/coverage.rst
+++ b/blog/draft/coverage.rst
@@ -52,7 +52,7 @@
 
 So how'd we do it? Previously, using ``sys.settrace()`` (which ``coverage.py``
 uses under the hood) disabled the JIT. Except it didn't just disable the JIT,
-it did it in a particularly insidious way, the JIT had no idea it was being
+it did it in a particularly insidious way &#8212; the JIT had no idea it was 
being
 disabled!
 
 Instead, every time PyPy discovered one of your functions was a hotspot, it
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
https://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to