| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Memory usage now matches that of _io for large files
|
Optimization enabled by gh-139871 (Trying to keep that one issue referencing all the things which I use it for; planning to expand the What's New with a single "here's all the modules that got faster" list once optimize) |
Sorry, something went wrong.
| @@ -620,15 +620,15 @@ def read(self, size=-1): | |||
| if n < 0 or n > len(b): | |||
| raise ValueError(f"readinto returned {n} outside buffer size {len(b)}") | |||
| del b[n:] | |||
There was a problem hiding this comment.
Is there a difference between b.resize(n) and del b[n:]?
Sorry, something went wrong.
There was a problem hiding this comment.
.resize() could grow while the del b[n:] never will. There's some code which does a = bytearray(b'12'); del a[3:] (intentionally del a slice past the end) as part of its buffer management. Generally I prefer resize because there's a lot less code involved than the slice code (and the slice code eventually calls resize anyways)
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
…1539) Memory usage now matches that of _io for large files.
| Back | FazBrowse Home | New Git URL |
Memory usage now matches that of _io for large files.
For reference; this test goes from 8.5sec overall duration on my AMD 64 bit Arch Linux box to 7 seconds.