On Wed, Apr 7, 2021 at 11:29 PM Miro Hrončok <mhron...@redhat.com> wrote: > > On 07. 04. 21 14:53, Inada Naoki wrote: > > 'U' mode was removed once and resurrected. > > https://bugs.python.org/issue39674 > > > > As far as I can see, it is postponed to Python 3.10. Am I right? > > Can we remove 'U' mode in Python 3.10? > > What is the benefit of doing it? Is the current compatibility layer to do > nothing when "U" is passed difficult to maintain? >
I am working on fileinput module: * https://bugs.python.org/issue43712 * https://bugs.python.org/issue5758 * https://bugs.python.org/issue36865 It supports deprecated 'U' mode for now, same to builtin open(). When I read and write code and tests, I need to pay attention about all allowed combination of mode string. It is not difficult to maintain, but it has significant support cost. If we don't remove it forever, accumulated cost would be very high than users think. It is technical debt. Regards, -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/YBT47H36E4IWMLOFATQEIJOTQEGZ4SQE/ Code of Conduct: http://python.org/psf/codeofconduct/
