bpo-43224: Implement substitution of unpacked TypeVarTuple#31800
bpo-43224: Implement substitution of unpacked TypeVarTuple#31800serhiy-storchaka merged 5 commits into
Conversation
da60f24 to
4fab260
Compare
March 10, 2022 18:55
|
Thanks for looking into this! |
Sorry, something went wrong.
|
Woah, I'm not sure merging this was a good idea. We discussed this extensively in #31021 (review) and decided against implementing it this way. There are too many edge cases (e.g. the merged implementation will happily assign an unpacked arbitrary-length tuple such as I'd strongly prefer this merge to be reversed in favour of #31804 and/or further discussion on what the right approach is. |
Sorry, something went wrong.
|
I think that Workaround can be used in cases where this does not work. |
Sorry, something went wrong.
|
If you're adamant about keeping this implementation, I don't feel happy about it, but I don't want this to become a blocker for us. I'll submit a new PR with extra test cases so we can be more confident we've covered the edge cases. |
Sorry, something went wrong.
https://bugs.python.org/issue43224