This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients benjamin.peterson, ezio.melotti, mrabarnett, serhiy.storchaka
Date 2017-05-14.12:16:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494764170.53.0.794863715798.issue30363@psf.upfronthosting.co.za>
In-reply-to
Content
The life of 2.7 is so long that our common practice of releasing one or two versions with warnings before removing a feature or changing the behavior in incompatible way doesn't work. People that will start porting to Python 3 in 2020 will be surprised.

Proposed patch backports warnings in the re module to 2.7 in py3k mode. Some of these warnings already are converted to errors, but the most important warnings are warnings about changing semantic. '\u' and '\U' have different meaning in 3.3+ (see issue3665). re.split() with potentially empty pattern now emits FutureWarning and will change the behavior in future versions (see issue22818).

Warnings about inline flags occurred not at the start of the regular expression (see issue22493 and issue30298) was not backported. Adding them requires changing the fnmatch module, non-trivially changing distutils, and likely will break third-party libraries.

Warnings are emitted only when Python is ran with the -3 option, and it is easy to fix regular expressions.
History
Date User Action Args
2017-05-14 12:16:10serhiy.storchakasetrecipients: + serhiy.storchaka, benjamin.peterson, ezio.melotti, mrabarnett
2017-05-14 12:16:10serhiy.storchakasetmessageid: <1494764170.53.0.794863715798.issue30363@psf.upfronthosting.co.za>
2017-05-14 12:16:10serhiy.storchakalinkissue30363 messages
2017-05-14 12:16:09serhiy.storchakacreate