homepage

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 r.david.murray
Recipients amaury.forgeotdarc, eric.araujo, mnewman, r.david.murray, tati_alchueyr, vstinner
Date 2012年03月13日.14:41:45
SpamBayes Score 6.839452e-05
Marked as misclassified No
Message-id <1331649705.82.0.466788255053.issue5758@psf.upfronthosting.co.za>
In-reply-to
Content
For 3.2 could we use the same fix, but without exposing the ability to *change* the encoding? That is, we use TextIOWrapper but always with the default None for encoding.
It also occurs to me that this really exposes a weakness in the design. What if the user wants to specify other open parameters? I wonder if we should say that for better future-proofing openhooks should always take **kw. You could even envision fileinput accepting **kw and passing them along to the openhook. I think charset is the most important open paramenter in this context, though, so I don't think we have to solve the general problem in this fix.
History
Date User Action Args
2012年03月13日 14:41:45r.david.murraysetrecipients: + r.david.murray, amaury.forgeotdarc, vstinner, eric.araujo, mnewman, tati_alchueyr
2012年03月13日 14:41:45r.david.murraysetmessageid: <1331649705.82.0.466788255053.issue5758@psf.upfronthosting.co.za>
2012年03月13日 14:41:45r.david.murraylinkissue5758 messages
2012年03月13日 14:41:45r.david.murraycreate

AltStyle によって変換されたページ (->オリジナル) /