diff options
| author | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-04-15 20:08:51 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2016-04-15 20:09:59 +0300 |
| commit | 53ac7830cb501834fee9dda0c081261c1b62997c (patch) | |
| tree | ec9247d973fd80f284194c8908f18708ad494adf /docs/reference/speed_python.rst | |
| parent | 2c883c5ab7722c2309da9d3121cf253105da1eb1 (diff) | |
| download | micropython-53ac7830cb501834fee9dda0c081261c1b62997c.tar.gz micropython-53ac7830cb501834fee9dda0c081261c1b62997c.zip | |
docs/speed_python: Add article.
Diffstat (limited to 'docs/reference/speed_python.rst')
| -rw-r--r-- | docs/reference/speed_python.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/reference/speed_python.rst b/docs/reference/speed_python.rst index 7bc4868054..2f1d16cea1 100644 --- a/docs/reference/speed_python.rst +++ b/docs/reference/speed_python.rst @@ -99,7 +99,7 @@ of slice it points too. A ``memoryview`` can only be applied to objects supporting the buffer protocol - this includes arrays but not lists. Small caveat is that while memoryview object is live, -it also keeps alive the original buffer object. So, memoryviews isn't universal +it also keeps alive the original buffer object. So, a memoryview isn't a universal panacea. For instance, in the example above, if you are done with 10K buffer and just need those bytes 30:2000 from it, it may be better to make a slice, and let the 10K buffer go (be ready for garbage collection), instead of making a |