➜

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 BreamoreBoy, Håkan Lövdahl, barry, eric.smith, jesstess, maciej.szulik, pitrou, r.david.murray, zvyn
Date 2015-05-05.22:27:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430864852.33.0.827814503854.issue21800@psf.upfronthosting.co.za>
In-reply-to
Content 
Well, the problem with that is that we then have to parse the capability to see if it is utf8 that is being enabled.  I don't like that as an API, it feels fragile.  Since capabilities cannot later be disabled, there's no functional reason to keep it separate.   However, it would solve the problem of values to use in the init flag, and would remove the caveat that you shouldn't use UTF8=ENABLE in an explicit enable call, so perhaps it is best after all.

Do you have any interest in updating the patch?  I won't be able to get back to it until this weekend.
History
Date User Action Args
2015-05-05 22:27:32r.david.murraysetrecipients: + r.david.murray, barry, pitrou, eric.smith, jesstess, BreamoreBoy, maciej.szulik, zvyn, Håkan Lövdahl
2015-05-05 22:27:32r.david.murraysetmessageid: <1430864852.33.0.827814503854.issue21800@psf.upfronthosting.co.za>
2015-05-05 22:27:32r.david.murraylinkissue21800 messages
2015-05-05 22:27:32r.david.murraycreate