GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — bpo-43224: Unpack concrete tuple types into a sequence of types by serhiy-storchaka · Pull Request #32030 · python/cpython Conversation
|
|
I'd rather not do this for the reasons @mrahtz explained elsewhere. Another point: what about |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should do this (see also @mrahtz's comment at #91162 (comment)):
Unpack[tuple[int, str]] not the same as *tuple[int, str].def f(*args: *tuple[int, str]) would end up with int in its __annotations__ because of the way we implemented * there.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
+1 to what @JelleZijlstra says. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.