Paul Moore p.f.moore at gmail.com
Fri Nov 25 16:48:23 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 ]

---

On 25 November 2011 15:07, Amaury Forgeot d'Arc <amauryfa at gmail.com> wrote:
> 2011/11/25 Paul Moore <p.f.moore at gmail.com>
>> It would be nice to have the optimisation back if it's easy enough to
>> do so, for quick-and-dirty code, but it is not a good idea to rely on
>> it (and it's especially unwise to base benchmarks on it working :-))
>
> Note that this string optimization hack is still present in Python 3,
> but it now acts on *unicode* strings, not bytes.

Ah, yes. That makes sense.
Paul

---

• 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 ]

---

More information about the Python-Dev mailing list