Author: Antonio Cuni <anto.c...@gmail.com> Branch: extradoc Changeset: r5927:85b946c1b8aa Date: 2018-12-23 14:45 +0100 http://bitbucket.org/pypy/extradoc/changeset/85b946c1b8aa/
Log: typo, thanks to René Dudfield diff --git a/blog/draft/2018-12-gc-disable/gc-disable.rst b/blog/draft/2018-12-gc-disable/gc-disable.rst --- a/blog/draft/2018-12-gc-disable/gc-disable.rst +++ b/blog/draft/2018-12-gc-disable/gc-disable.rst @@ -75,7 +75,7 @@ Combining these two functions, it is possible to take control of the GC to make sure it runs only when it is acceptable to do so. For an example of usage, you can look at the implementation of a `custom GC`_ inside pypytools_. -The peculiarity is that is also defines a ``with nogc():`` context manager +The peculiarity is that it also defines a ``with nogc():`` context manager which you can use to mark performance-critical sections where the GC is not allowed to run. _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit
