Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[3.8] bpo-32912: Revert warnings for invalid escape sequences. #15142

Merged
merged 3 commits into from
Aug 9, 2019
Merged

[3.8] bpo-32912: Revert warnings for invalid escape sequences. #15142

merged 3 commits into from
Aug 9, 2019

Commits on Aug 6, 2019

  1. bpo-32912: Revert warnings for invalid escape sequences. 

    DeprecationWarning will continue to be emitted for invalid
escape sequences in string and bytes literals in 3.8.
SyntaxWarning will be emitted in 3.9.
    @serhiy-storchaka
    serhiy-storchaka committed Aug 6, 2019
    Configuration menu
    Copy the full SHA
    5d4c998 View commit details
    Browse the repository at this point in the history

Commits on Aug 7, 2019

  1. Fix a typo.

    @serhiy-storchaka
    serhiy-storchaka committed Aug 7, 2019
    Configuration menu
    Copy the full SHA
    1775d3f View commit details
    Browse the repository at this point in the history

Commits on Aug 8, 2019

  1. update the wording to not promise 3.9 

    and mention that SyntaxError will happen after SyntaxWarning.  we're being non-specific on purpose here as we haven't worked out the plan to make this happen without causing end user pain yet.  right now most code owners do not see the DeprecationWarning but when turned into a SyntaxWarning, _users_ of libraries see it more often than owners.  So it is a negative experience all around.
    @gpshead
    gpshead authored Aug 8, 2019
    Configuration menu
    Copy the full SHA
    3f58e3f View commit details
    Browse the repository at this point in the history