[Python-Dev] file.readinto performance regression in Python 3.2 vs. 2.7? (original) (raw)
Matt Joiner anacrolix at gmail.com
Fri Nov 25 02:02:17 CET 2011
- Previous message: [Python-Dev] file.readinto performance regression in Python 3.2 vs. 2.7?
- Next message: [Python-Dev] file.readinto performance regression in Python 3.2 vs. 2.7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It's my impression that the readinto method does not fully support the buffer interface I was expecting. I've never had cause to use it until now. I've created a question on SO that describes my confusion:
http://stackoverflow.com/q/8263899/149482
Also I saw some comments on "top-posting" am I guilty of this? Gmail defaults to putting my response above the previous email.
On Fri, Nov 25, 2011 at 11:49 AM, Matt Joiner <anacrolix at gmail.com> wrote:
Eli,
Example coming shortly, the differences are quite significant. On Fri, Nov 25, 2011 at 9:41 AM, Eli Bendersky <eliben at gmail.com> wrote: On Fri, Nov 25, 2011 at 00:02, Matt Joiner <anacrolix at gmail.com> wrote:
What if you broke up the read and built the final string object up. I always assumed this is where the real gain was with readinto. Matt, I'm not sure what you mean by this - can you suggest the code? Also, I'd be happy to know if anyone else reproduces this as well on other machines/OSes. Eli
- Previous message: [Python-Dev] file.readinto performance regression in Python 3.2 vs. 2.7?
- Next message: [Python-Dev] file.readinto performance regression in Python 3.2 vs. 2.7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]