[issue28403] Porting guide: disabling & warning on implicit unicode conversions

Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- nosy: +serhiy.storchaka resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue28403] Porting guide: disabling & warning on implicit unicode conversions

Brett Cannon added the comment: If a new codec gets added to 2.7 then I'm fine with the proposed change. -- ___ Python tracker ___

[issue28403] Porting guide: disabling & warning on implicit unicode conversions

Marc-Andre Lemburg added the comment: On 10.10.2016 15:08, Petr Viktorin wrote: > If sys.setdefaultencoding('undefined') breaks parts of the standard library, > it might be OK for smaller scripts but I fear it won't help big projects much. That's true. It does break the stdlib (the codec was

[issue28403] Porting guide: disabling & warning on implicit unicode conversions

Petr Viktorin added the comment: In portingguide [0] I could only recommend sitecustomize with a (possibly third-party) codec that emits warnings; not 'undefined'. The things that aren't ported yet are generally either Non-Python applications with Python bindings or plugins (Gimp, Samba,

[issue28403] Porting guide: disabling & warning on implicit unicode conversions

Nick Coghlan added the comment: Adding Petr to the nosy list, as I'd like to get his perspective on this once I have a draft docs patch to review. I also realised it made more sense to just repurpose this issue to cover the proposed docs updates. -- assignee: -> docs@python