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

Backport "Migration rewrites for infix arguments interpreted as named tuples" to 3.6 #21966

Merged
merged 1 commit into from
Nov 18, 2024
Merged

Backport "Migration rewrites for infix arguments interpreted as named tuples" to 3.6 #21966

merged 1 commit into from
Nov 18, 2024

Commits on Nov 18, 2024

  1. Migration rewrites for infix arguments interpreted as named tuples (#… 

    …21949)

Best effort migration rewrites based on prior work in #21565  

At this point, it's too late to deprecate named infix arguments. Let's
produce warnings instead. We accept infix arguments that might be an
argument of a named tuple, eg. `zip`, `++` or `==` - each of these takes
a single argument with NamedTuple.

---------

Co-authored-by: Som Snytt <[email protected]>
Co-authored-by: Matt Bovel <[email protected]>
[Cherry-picked 5d5a9e6]
    @WojciechMazur
    WojciechMazur committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    3e4d48d View commit details
    Browse the repository at this point in the history