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

[Serhiy Storchaka]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Brett Cannon]

Brett Cannon added the comment:

If a new codec gets added to 2.7 then I'm fine with the proposed change.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Marc-Andre Lemburg]

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 originally
added in order to test exactly this scenario).

A new codec "ascii-warn" could easily be added, based on the
code used for "undefined".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Petr Viktorin]

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, ...), projects that are very 
large relative to the count of available maintainers (VCSs, Sugar, wxPython, 
...), or code that depends on those.

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.


[0] http://portingguide.readthedocs.io/en/latest/

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Nick Coghlan]

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
components: +Documentation
nosy: +docs@python, encukou
stage:  -> needs patch
title: Migration RFE: optional warning for implicit unicode conversions -> 
Porting guide: disabling & warning on implicit unicode conversions

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com