On 12/3/19 8:13 PM, Inada Naoki wrote:
I think it is too early to determine when to remove it.
Even only talking about it causes blaming war.
Has anyone yet given a reason to remove it? It will change working code
into broken code. Why do that?
--Ned.
BTW, I think 2to3 can help to move from 2&3 code to 3-only code.
* "future" fixer can be remove legacy futures. But it seems to remove
all futures,
including "annotations". It should be kept.
* "unicode" fixer can be used to remove u-prefix. But I'm not sure yet.
Are there any other things which are used for writing 2&3 code and
will be removed
someday in the future?
And is there any tool that can convert code using the "six" library to
normal Python 3 code?
Regards,
On Wed, Dec 4, 2019 at 2:29 AM Serhiy Storchaka <storch...@gmail.com> wrote:
The 'u" string literal prefix was removed in 3.0 and reintroduced in 3.3
to help writing the code compatible with Python 2 and 3 [1]. After the
dead of Python 2.7 we will remove some deprecated features kept for
compatibility with 2.7. When we are going to deprecate and remove the
"u" prefix?
[1] https://www.python.org/dev/peps/pep-0414/
_______________________________________________
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/EMFDKQ57JVWUZ6TPZM5VTFW7EUKVYAOY/
Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________
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/27OFJ45B4OFDR3ON2QI72XDF7ISVADU3/
Code of Conduct: http://python.org/psf/codeofconduct/
