This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients amaury.forgeotdarc, beazley, christian.heimes, donmez, georg.brandl, giampaolo.rodola, pitrou, rhettinger, wplappert
Date 2008-12-16.13:26:58
SpamBayes Score 0.00065177627
Marked as misclassified No
Message-id <1229434020.01.0.593219777625.issue4561@psf.upfronthosting.co.za>
In-reply-to
Content
I don't agree that that was a worthy design goal.  Tons of code (incl
the old CPython successfully used the stdlib functions).  IMO, a 3x or
4x falloff for binary reads/writes is a significant disincentive for
adopting Py3.0.  For binary reads/writes, I would like to see the open()
factory function return the old, fast object instead to trying to slowly
simulate it without adding any benefits noticeable to an end-user.  IMO,
it's a case of practicality beating purity.
History
Date User Action Args
2008-12-16 13:27:00rhettingersetrecipients: + rhettinger, georg.brandl, beazley, amaury.forgeotdarc, pitrou, giampaolo.rodola, christian.heimes, donmez, wplappert
2008-12-16 13:27:00rhettingersetmessageid: <1229434020.01.0.593219777625.issue4561@psf.upfronthosting.co.za>
2008-12-16 13:26:59rhettingerlinkissue4561 messages
2008-12-16 13:26:58rhettingercreate