On 3/15/19 4:54 AM, Stephen J. Turnbull wrote: > What 2to3 does is to handle a lot of automatic conversions, such as > flipping the identifiers from str to bytes and unicode to str. It was > necessary to have some such tool because of the very large amount of > such menial work needed to change a 2 code base to a 3 code base. But > even so, there were things that 2to3 couldn't do, and it often exposed > bugs or very poor practice (decode applied to unicode objects, encode > applied to bytes) that had to be reworked by the developer anyway. Very interesting from the 2/3 transition experience point of view. But that's not still the past, IMHO that will be after 2020,... around 2025 :-)
Could one also say that under the line that it *improved* the code? (by exposing bugs, bad practices) could be a first step to just *flag* those behaviors/changes ? Regards, --francis _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/